Ticketmaster Partner API
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TM_PARTNER_API_KEY | Yes | Your Ticketmaster Partner API key | |
| TM_PARTNER_API_SECRET | Yes | Your Ticketmaster Partner API secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tm_partnerC | Search for events, venues, or attractions using Ticketmaster Partner API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity with other tools. The tool's purpose is clearly defined as searching for events, venues, or attractions.
With a single tool, naming consistency is trivially maintained. The name 'search_tm_partner' follows a clear snake_case verb_noun pattern.
One tool is too few for a server named 'Ticketmaster Partner API', which implies a broader set of operations beyond search. The tool count feels severely limited given the domain scope.
The server only offers a search tool, leaving out essential operations like retrieving event details, managing orders, or performing CRUD actions. This creates significant gaps that prevent an agent from accomplishing typical tasks with the API.