Skip to main content
Glama

Ticketmaster

by io.github.pipeworx-io

Event Search

event_search
Read-onlyIdempotent

Ticketmaster Discovery API — search live events by keyword, city, countryCode, stateCode, venueId, attractionId, classificationName (e.g. 'Music'), and date window. PREFER for "what is on at ", "upcoming concerts", "events in this month". Pass the venue/artist as keyword, or venueId from venue_search for an exact venue. Returns events with dates, venue, and ticket links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity name, e.g. "New York".
pageNo0-based page number. Ticketmaster caps deep paging at page × size ≤ 1000, so with the default size of 20 the last reachable page is 50; narrow with city/date filters instead of paging further.
sizeNoResults per page (default 20, max 200).
sortNoSort order. Ticketmaster accepts only these values; anything else is a 400. Common: "date,asc" (soonest first), "relevance,desc".
keywordNoFree-text search: venue, artist, team or event name (e.g. "Madison Square Garden", "Taylor Swift"). Pass the subject of the question here — omitting it returns Ticketmaster's unfiltered default feed, not an answer.
venueIdNoTicketmaster venue id (from venue_search). More precise than keyword for "what is on at <venue>" — a keyword can match a nearby or similarly named venue.
stateCodeNo2-letter state code, e.g. "NY".
postalCodeNoPostal/ZIP code.
countryCodeNo2-letter country code, e.g. "US".
endDateTimeNoISO-8601 UTC upper bound, e.g. "2026-08-31T23:59:59Z".
attractionIdNoTicketmaster attraction id (from attraction_search).
startDateTimeNoISO-8601 UTC lower bound, e.g. "2026-08-01T00:00:00Z". Use with endDateTime for "this month".
classificationNameNoSegment/genre, e.g. "Music", "Sports", "Theatre".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "keyword": "taylor swift"
-  },
-  {
-    "city": "new york",
-    "keyword": "concert",
-    "startDateTime": "2024-01-01T00:00:00Z"
-  }
-]New value: +[
+  {
+    "keyword": "taylor swift"
+  },
+  {
+    "city": "new york",
+    "keyword": "concert",
+    "startDateTime": "2024-01-01T00:00:00Z"
+  },
+  {
+    "keyword": "Taylor Swift",
+    "size": 2,
+    "sort": "date,asc"
+  }
+]
    • changedInput schema / properties / page / description
      Previous value: -"0-based page number."New value: +"0-based page number. Ticketmaster caps deep paging at page × size ≤ 1000, so with the default size of 20 the last reachable page is 50; narrow with city/date filters instead of paging further."
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order, e.g. \"date,asc\" or \"relevance,desc\"."New value: +"Sort order. Ticketmaster accepts only these values; anything else is a 400. Common: \"date,asc\" (soonest first), \"relevance,desc\"."
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "name,asc",
+  "name,desc",
+  "date,asc",
+  "date,desc",
+  "relevance,asc",
+  "relevance,desc",
+  "distance,asc",
+  "distance,date,asc",
+  "name,date,asc",
+  "name,date,desc",
+  "date,name,asc",
+  "date,name,desc",
+  "onSaleStartDate,asc",
+  "id,asc",
+  "venueName,asc",
+  "venueName,desc",
+  "random"
+]
  2. Changed13 schema fields changed
    • addedInput schema / properties / attractionId
      Added value: +{
+  "description": "Ticketmaster attraction id (from attraction_search).",
+  "type": "string"
+}
    • addedInput schema / properties / city
      Added value: +{
+  "description": "City name, e.g. \"New York\".",
+  "type": "string"
+}
    • addedInput schema / properties / classificationName
      Added value: +{
+  "description": "Segment/genre, e.g. \"Music\", \"Sports\", \"Theatre\".",
+  "type": "string"
+}
    • addedInput schema / properties / countryCode
      Added value: +{
+  "description": "2-letter country code, e.g. \"US\".",
+  "type": "string"
+}
    • addedInput schema / properties / endDateTime
      Added value: +{
+  "description": "ISO-8601 UTC upper bound, e.g. \"2026-08-31T23:59:59Z\".",
+  "type": "string"
+}
    • addedInput schema / properties / keyword
      Added value: +{
+  "description": "Free-text search: venue, artist, team or event name (e.g. \"Madison Square Garden\", \"Taylor Swift\"). Pass the subject of the question here — omitting it returns Ticketmaster's unfiltered default feed, not an answer.",
+  "type": "string"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "0-based page number.",
+  "type": "number"
+}
    • addedInput schema / properties / postalCode
      Added value: +{
+  "description": "Postal/ZIP code.",
+  "type": "string"
+}
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Results per page (default 20, max 200).",
+  "type": "number"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "Sort order, e.g. \"date,asc\" or \"relevance,desc\".",
+  "type": "string"
+}
    • addedInput schema / properties / startDateTime
      Added value: +{
+  "description": "ISO-8601 UTC lower bound, e.g. \"2026-08-01T00:00:00Z\". Use with endDateTime for \"this month\".",
+  "type": "string"
+}
    • addedInput schema / properties / stateCode
      Added value: +{
+  "description": "2-letter state code, e.g. \"NY\".",
+  "type": "string"
+}
    • addedInput schema / properties / venueId
      Added value: +{
+  "description": "Ticketmaster venue id (from venue_search). More precise than keyword for \"what is on at <venue>\" — a keyword can match a nearby or similarly named venue.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile needs no restating, and the description wisely avoids doing so. It adds the external-provider identity (Ticketmaster Discovery API) and the rough return shape (dates, venue, ticket links) which sets correct expectations about what 'search' produces. It stops short of covering rate limits or response-volume edge cases, but that is a minor gap given how much the annotations carry.

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

Conciseness4/5

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

Four sentences, front-loaded with purpose and closing on return shape; the 'PREFOR' marker is a crisp structural cue. The middle sentence's parameter list partially overlaps with what the schema already renders, and 'Returns events with dates, venue, and ticket links' slightly duplicates the output schema — but nothing is bloated or self-indulgent.

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

Completeness5/5

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

For a 13-parameter, zero-required-parameter search tool, this is complete: it answers what it does, when to prefer it, how to phrase queries, and how to disambiguate via venue_search for exactness. The 100%-covered schema and output schema carry the operational minutiae (paging caps, sort enums), and the description delivers the strategic decision layer that structured fields cannot express.

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 baseline of 3 applies. The description groups parameters into conceptual buckets (date window, venueId-for-exact-venue) which helps the keyword-vs-venueId decision, but all the deep semantics (paging cap, sort whitelist, empty-keyword default feed) live exclusively in the schema. The description complements rather than compensates for 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?

Opens with a specific verb+resource ('search live events') and names the provider (Ticketmaster Discovery API), then enumerates seven explicit filter dimensions plus a date window. The three usage examples ('what is on at <venue>', 'upcoming <artist> concerts', 'events in <city> this month') leave zero ambiguity about what resource is being operated on, making it self-evidently distinct from siblings like event (singular) and venue_search.

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

Usage Guidelines5/5

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

The 'PREFER for...' sentence explicitly enumerates the canonical query patterns, and the third sentence routes the agent between keyword search and using venueId from venue_search for exact-venue matches. It names an alternative tool and the condition that selects it — the agent is told exactly when to reach for this tool versus a sibling, and no inference is required.

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

All Ticketmaster toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.9/5.0
Disambiguation2/5

The tools fall into two unrelated domains (Ticketmaster event discovery and Pipeworx data research), and within the Pipeworx set there are near-duplicate tools like ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded, plus multiple overlapping prediction-market tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, etc.). An agent would struggle to choose among these overlapping options and may not realize that most tools are unrelated to the server's stated name.

Naming Consistency3/5

Naming uses consistent snake_case, but the pattern is mixed: Ticketmaster resource fetchers are bare nouns (event, venue, attraction, classification) while search tools use verb_noun (event_search, venue_search). Pipeworx tools vary between verb phrases (ask_pipeworx, validate_claim) and descriptive noun phrases (entity_profile, polymarket_kalshi_spread). This inconsistency makes predicting tool names harder, though each name is still readable.

Tool Count2/5

41 tools is excessive for a server titled 'Ticketmaster' when only about 10 are Ticketmaster-related; the other 30 cover an entirely different service (Pipeworx). The count is far beyond a focused scope and suggests the server should be split into two separate, well-scoped MCP servers.

Completeness4/5

For the Ticketmaster half, the surface is complete for read-only event discovery (search events/venues/attractions, get single resources, classifications, autocomplete). For the Pipeworx half, the tool suite is extensive, covering lookup, research, prediction markets, memory, subscriptions, and feedback. The only notable gap is the lack of any write operations, but this is consistent with the read-only nature of the underlying APIs.

Resources