MCP server for Ticketmaster - let AI agents search events, check availability, select seats, and purchase tickets
Server has 14 well-named tools with consistent verb_noun patterns (ticketmaster_*). All tools have descriptions (10 - 200 chars, within baseline 34 - 392 range). Input schemas are present and properly typed for all tools. However, output schemas are completely undocumented, LLMs cannot predict response structure for downstream chaining. Parameter descriptions are adequate but lack format constraints (e.g., date format, price ranges, quantity limits). Error handling is absent from visible code, no recovery guidance, retryability classification, or actionable error messages. The checkout tool correctly implements a confirmation pattern but lacks explicit dry-run documentation. No security annotations visible (scope declarations, permission gates). Overall: solid naming and basic schema structure, but missing output documentation and error guidance that would elevate this to 70+.
Add tickets to the Ticketmaster cart for an event.
Check ticket availability for a specific event. Returns availability status and section info.
Purchase tickets. IMPORTANT: Set confirm=true only when you have explicit user confirmation. Without confirm=true, this returns a cart preview instead of purchasing.
Get detailed information about a specific event by event ID or URL.
Get Ticketmaster order history. Requires being logged in.
Get price ranges for a specific event, including all ticket tiers and fee estimates.
Output schemas completely undocumented. LLMs cannot predict response structure (fields, types, nesting) for any tool. This breaks downstream tool chaining and forces agents to guess field names.
No error handling or recovery guidance in visible code. Tools lack actionable error messages, retryability classification, or suggestions for next steps. Agents cannot self-correct on failures.
Parameter constraints missing. Numeric parameters (quantity, maxResults, maxPrice) lack min/max bounds. Date parameters lack format validation. LLMs can pass invalid values (negative quantities, dates in wrong format).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Get detailed information about a specific venue by venue ID or URL.
Search for venues near a location.
Initiate Ticketmaster login flow. Returns a URL and instructions for the user to complete login manually. After logging in, use ticketmaster_status to verify.
Clear saved Ticketmaster session and cookies. Use this to log out or reset authentication state.
Search for events on Ticketmaster. Returns event names, dates, venues, and price ranges.
Select seats/tickets for an event. Returns selected ticket details. Does NOT add to cart yet.
Check Ticketmaster login status and session info. Use this to verify authentication before performing other actions.
View current Ticketmaster cart contents, including events, seats, and totals.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe read-only tools from destructive ones without reading descriptions. checkout tool is IRREVERSIBLE but lacks explicit annotation.
No scope declarations or permission gates visible. Tools that modify state (login, add_to_cart, checkout) lack explicit permission requirements. No audit trail or security context documented.