MCP server for integrating with Luma Events API to manage events, guests, and invitations
Server has 9 tools with complete input schemas and descriptions. Naming follows verb_noun convention (create_event, get_event, list_events, etc.). Descriptions are present but generic, most are 50-150 chars and lack context on WHEN to use each tool or dependencies between them. Parameters are typed (string, object, array) with descriptions, but lack constraints (enums, ranges, patterns). No output schemas documented. Error handling is minimal, tools return raw API responses without recovery guidance. Missing tool annotations (readOnlyHint, destructiveHint). Composition is reasonable: tools are single-purpose and chainable (e.g., create_event → send_invites). Security: API key injected via environment variable (good), but no permission gates or audit logging.
Add a host to a Luma event. Args: event_id: The unique identifier of the event (e.g., "evt-ABC123") email: Email address of the host to add name: Name of the host (ignored if they already have a Luma profile) Returns: Result of adding host or an error message
Create a new Luma event. Args: name: The title of the event start_at: Start time in ISO 8601 format (e.g., "2024-12-31T23:59:00Z") location: Event location with place_id (Google Maps) and optional description end_at: End time in ISO 8601 format (optional) description_md: Event description in Markdown format (optional) cover_url: URL for the event cover image (optional) Returns: The created event data or an error message
Get all unique guests from all past events. Returns: De-duplicated list of Guest objects (by email)
Get details about a Luma event. Args: event_id: The unique identifier of the event (e.g., "evt-ABC123") Returns: The event data or an error message
Get a specific guest for a Luma event. Args: event_id: The unique identifier of the event (e.g., "evt-ABC123") guest_id: The unique identifier of the guest Returns: Guest data or an error message
No output schemas documented. LLMs cannot predict response structure or plan downstream tool calls. E.g., create_event returns 'The created event data' but no field list.
Descriptions lack WHEN-to-use context and dependencies. E.g., 'Get details about a Luma event' does not explain when to call get_event vs list_events, or that event_id is required from a prior call.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLMs cannot distinguish safe reads from destructive writes. create_event, update_event, send_invites, add_host should be marked destructive.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | <=2025-11-25 | v2 |
Get all guests for a Luma event. Args: event_id: The unique identifier of the event (e.g., "evt-ABC123") Returns: List of guests or an error message
List all events for the default calendar. Returns: List of events or an error message
Send invites to guests for a Luma event. Args: event_id: The unique identifier of the event (e.g., "evt-ABC123") guests: List of Guest objects with email (required) and name (optional) Returns: Result of sending invites or an error message
Update an existing Luma event. Args: event_id: The unique identifier of the event to update (api_id) name: New title for the event (optional) description_md: New description in Markdown format for the event (optional) start_at: New start time in ISO 8601 format (optional) end_at: New end time in ISO 8601 format (optional) cover_url: New URL for the event cover image (optional) location: New event location (optional) Returns: The updated event data or an error message
Parameters lack constraints. E.g., 'start_at' accepts any string but should enforce ISO 8601 format. 'location' object has no required field markers. No enums, ranges, or patterns.
Error handling is absent. Tools return raw API responses (e.g., {'error': 'LUMA_API_KEY not set'}) without recovery guidance. LLMs cannot determine if errors are retryable or user-fixable.