Ticketmaster MCP integration for AI agents.
Connect AI agents to Ticketmaster through 15 structured actions, including get attraction details, execute season ticketing command, and get attractions. Rev…
- ACTION CONTRACTS
- 15
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Ticketmaster integration exposes
The Ticketmaster Agent App exposes 15 provider-backed actions for social and data work. Its current contract lets an authorized agent get the details for a specific ticketmaster attraction by id, execute a ticketmaster season ticketing command, and search discovery api attractions. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Ticketmaster account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Ticketmaster capabilities.
Showing 12 of 15 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_attraction_detailsREADGet the details for a specific Ticketmaster attraction by ID.
INPUTS: id / locale / domain
execute_season_ticketing_commandWRITEExecute a Ticketmaster Season Ticketing command.
INPUTS: product / header / command / cookies / maxPollAttempts
get_attractionsREADSearch Discovery API attractions.
get_classification_detailsREADGet a Ticketmaster classification by ID.
INPUTS: id / locale / domain
get_classificationsREADSearch Ticketmaster classifications.
get_event_detailsREADGet the details for a specific Ticketmaster event by ID.
INPUTS: id / locale / domain
get_event_imagesREADGet the image set for a specific Ticketmaster event.
INPUTS: id / locale / domain
get_eventsREADSearch Discovery API events with Ticketmaster filters.
get_genre_detailsREADGet a Ticketmaster genre by ID.
INPUTS: id / locale / domain
get_section_map_imageREADRetrieve a Ticketmaster section-map image as base64.
INPUTS: eventId / systemId / placeId / sectionNames / domain
get_segment_detailsREADGet a Ticketmaster segment by ID.
INPUTS: id / locale / domain
get_subgenre_detailsREADGet a Ticketmaster sub-genre by ID.
INPUTS: id / locale / domain
INPUT CONTRACTS
Know what the action needs before it runs.
get_attraction_details
idREQUIRED- The Ticketmaster entity identifier.
localeOPTIONAL- The locale filter.
domainOPTIONAL- The region or domain filter.
execute_season_ticketing_command
productOPTIONAL- The Season Ticketing product path segment.
headerREQUIRED- The Season Ticketing request header.
commandREQUIRED- The Season Ticketing command payload.
cookiesOPTIONAL- Cookie values to send while polling.
maxPollAttemptsOPTIONAL- Maximum polling attempts.
get_classification_details
idREQUIRED- The Ticketmaster entity identifier.
localeOPTIONAL- The locale filter.
domainOPTIONAL- The region or domain filter.
get_event_details
idREQUIRED- The Ticketmaster entity identifier.
localeOPTIONAL- The locale filter.
domainOPTIONAL- The region or domain filter.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Attraction Details
Get the details for a specific Ticketmaster attraction by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_attraction_detailsControl Execute Season Ticketing Command
Execute a Ticketmaster Season Ticketing command. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
execute_season_ticketing_commandVerify with Get Attractions
Search Discovery API attractions. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_attractionsSAFETY BOUNDARY
Operate Ticketmaster with explicit limits
- Authorize Ticketmaster with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Ticketmaster rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Ticketmaster task completed successfully.
CONNECTION MODEL
API key
Ticketmaster developer API key used as the apikey query parameter for Discovery and Partner APIs, and as the apikey header for Season Ticketing.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 14
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Ticketmaster.