Ticketmaster

Venue Search

venue_search

Read-onlyIdempotent

Ticketmaster Discovery API — search venues by keyword, city, stateCode, countryCode, or postalCode. Returns venue name, address, city, state, capacity, coordinates and the venue id to pass to event_search as venueId.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City name, e.g. "New York".
`page`	No	0-based page number. Deep paging is capped at page × size ≤ 1000.
`size`	No	Results per page (default 20).
`sort`	No	Sort order. Ticketmaster accepts only these values for venues; anything else is a 400.
`keyword`	No	Venue name to search for, e.g. "Madison Square Garden".
`stateCode`	No	2-letter state code, e.g. "NY".
`postalCode`	No	Postal/ZIP code.
`countryCode`	No	2-letter country code, e.g. "US".

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 21, 2026

addedInput schema / properties / page

Added value: +{
+  "description": "0-based page number. Deep paging is capped at page × size ≤ 1000.",
+  "type": "number"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "Sort order. Ticketmaster accepts only these values for venues; anything else is a 400.",
+  "enum": [
+    "name,asc",
+    "name,desc",
+    "relevance,asc",
+    "relevance,desc",
+    "distance,asc",
+    "distance,desc",
+    "random"
+  ],
+  "type": "string"
+}

Changed6 schema fields changedAug 1, 2026

addedInput schema / properties / city

Added value: +{
+  "description": "City name, e.g. \"New York\".",
+  "type": "string"
+}

addedInput schema / properties / countryCode

Added value: +{
+  "description": "2-letter country code, e.g. \"US\".",
+  "type": "string"
+}

addedInput schema / properties / keyword

Added value: +{
+  "description": "Venue name to search for, e.g. \"Madison Square Garden\".",
+  "type": "string"
+}

addedInput schema / properties / postalCode

Added value: +{
+  "description": "Postal/ZIP code.",
+  "type": "string"
+}

addedInput schema / properties / size

Added value: +{
+  "description": "Results per page (default 20).",
+  "type": "number"
+}

addedInput schema / properties / stateCode

Added value: +{
+  "description": "2-letter state code, e.g. \"NY\".",
+  "type": "string"
+}

First observedMay 25, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, so the safety burden is carried. The description adds limited context on top: it discloses the underlying Ticketmaster Discovery API and notes the return fields, but does not address rate limits, auth, or pagination behavior. No contradiction with annotations.

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

Conciseness5/5

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

Two sentences, front-loaded with the core action then the result contract. The clause about passing venueId to event_search is essential and compact. No filler.

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

Completeness4/5

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

For an 8-param optional-field tool with an output schema and safe annotations, the description is largely complete—it covers intent, the result shape at a high level, and downstream. It does not note whether at least one filter should be provided when none are required, but that is a minor gap.

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 coverage is 100%, so the parameters are already documented individually. The description consolidates the filter list into one sentence and also not adds the notion that the resulting venue id is meaningful to event_search, but overall it adds little meaning beyond the schema.

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

Purpose5/5

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

The description states a specific action ('search venues') and the resource itself, lists distinct search dimensions, and indicates the return data (venue listing details). It also frames the output's role as supplying a venueId to event_search, which separates it from sibling 'venue' (singular).

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

Usage Guidelines4/5

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

The description explicitly tells the agent that the returned venue id should be passed to event_search as a venueId, giving a concrete workflow decision. It does not, however, mention when to prefer venue (singular) over venue_search, leaving that sibling routing implicit.

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

All Ticketmaster tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.