Skip to main content
Glama
robandrewford

Ticketmaster Partner API

search_tm_partner

Find events, venues, and attractions by keyword, location, or category. Filter results by date, city, and classification to get targeted listings.

Instructions

Search for events, venues, or attractions using Ticketmaster Partner API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesType of search to perform
keywordNoSearch keyword or term
eventIdNoSpecific event ID to retrieve
venueIdNoSpecific venue ID to search or retrieve
attractionIdNoSpecific attraction ID to search or retrieve
startDateTimeNoStart date/time in ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ)
endDateTimeNoEnd date/time in ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ)
cityNoCity name
stateCodeNoState code (e.g., NY, CA)
countryCodeNoCountry code (e.g., US, CA)
postalCodeNoPostal/ZIP code
latlongNoLatitude,longitude for geographic search
radiusNoSearch radius
unitNoUnit for radius (miles or km)
classificationNameNoEvent classification/category names
sizeNoNumber of results per page (max 200)
pageNoPage number (0-indexed)
sortNoSort order for results
formatNoOutput format (defaults to json)json
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It only says 'Search' but does not disclose behavioral traits such as rate limits, authentication requirements, or what happens with invalid parameters. The description is too minimal for a tool with 19 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but given the complexity of the tool (19 parameters, many optional), it is under-specified. Structure is lacking as there is no breakdown of usage patterns or parameter grouping.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 19 parameters and no output schema, the description is highly incomplete. It does not explain how parameters interact, what the response format is, or any constraints like required combinations. The tool is complex, and the description fails to provide sufficient context for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds no parameter-specific meaning beyond what the schema provides, but it does not contradict the schema either. The generic description does not compensate for any missing schema details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it searches for events, venues, or attractions using the Ticketmaster Partner API. It uses a specific verb and identifies the resource types. However, it does not mention that the tool can also retrieve by specific IDs (eventId, venueId, attractionId), which is a minor gap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool or how it compares to alternatives. There are no sibling tools listed, but even without alternatives, there is no context on use cases or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robandrewford/mcp-server-tm-partner'

If you have feedback or need assistance with the MCP directory API, please join our Discord server