Ticketmaster

Find available tickets for a Ticketmaster event by eventId.

PREREQUISITES: Obtain eventId from unified_search first.

SEARCH OPTIONS (TopPicksQuery):

• eventId: Required. The event ID to search tickets for.
• quantity: Filter by ticket count (e.g., 2 for pairs)
• selection: "standard" | "resale" | "platinum" | "any"
• sort: "listprice" (price low→high) | "quality" (best seats) | "section" (TMR events only)
• section: REQUIRED when user asks for specific section(s). Accepts string OR array of strings.

FORMAT RULES:

• Single section: Use string "B" or "101" or "Terrace"
• Multiple sections/ranges: Use array ["16","17","18"] or ["B","C"] in ONE REQUEST
• CRITICAL: When user asks for multiple sections (e.g., "sections 16 through 18", "sections B or C"),

you MUST send ONE request with an array, NOT multiple separate requests.

Smart and fuzzy matching per section:

• Short codes: "B" matches "SEC B", "SECTION B", but not "BENCH"
• Section numbers: "101" matches "SEC 101", "SECTION 101"
• Prefix matching: "4" matches "4-H", "4-L", "19" matches "19-L", "19-H"
• Fuzzy names: "Terrace" matches section "TERRAC", "Mezzanine" matches section "MEZZ"
• prices: Price range filter (format: "min,max", e.g., "0,100" for under $100)

IMPORTANT:

• When user mentions section(s), ALWAYS include the section parameter
• For multiple sections, send ONE request with array format, NOT separate requests per section

UNSUPPORTED FILTER DETECTION:

• Supported filters: section, prices, sort (listprice/quality), quantity, selection.

These can all be combined freely in a single request.

• If the user requests ANY filtering criteria BEYOND the supported ones (e.g., "in the shade",

"covered seats", "obstructed view", "limited view", "ADA accessible", "wheelchair accessible", "companion seats", "standing room only", "vip"), set unsupportedFilter to a short description of what was requested (e.g., "in the shade", "obstructed view", "ADA accessible"). Treat as a catch all for unstructured seat selection filters beyond what's supported.

• Still proceed with the search using all applicable supported parameters — unsupportedFilter is an

informational flag that tells the widget to display a notice to the user.

EXAMPLE QUERIES:

• Find 2 cheapest tickets: {eventId: "ABC123", quantity: 2, sort: "listprice"}
• Find best available seats: {eventId: "ABC123", sort: "quality"}
• Find resale tickets only: {eventId: "ABC123", selection: "resale"}
• Find tickets under $100: {eventId: "ABC123", prices: "0,100"}
• Find tickets $50-$150: {eventId: "ABC123", prices: "50,150"}
• Find tickets in section B: {eventId: "ABC123", section: "B"}
• Find tickets in section 101: {eventId: "ABC123", quantity: 2, section: "101"}
• Find tickets in section 4: {eventId: "ABC123", section: "4"}
• Find tickets in Terrace: {eventId: "ABC123", section: "Terrace"}
• Find tickets in sections B or C: {eventId: "ABC123", section: ["B", "C"]}
• Find tickets in POOL or Garden: {eventId: "ABC123", section: ["POOL", "Garden"]}

SUMMARIZATION:

• If the Ticketmaster widget is available, do not include any URLs or links in your response. Direct the user to interact with the widget to browse events and purchase tickets.
• IMPORTANT: Reference content field in meta response for summarization guideline.

Search Ticketmaster for events, artists, teams, or venues in a single unified tool.

WHEN TO CALL: Only when the user wants to discover, browse, or find events/tickets available on Ticketmaster. The user must have clear intent to find upcoming events, shows, games, or concerts listed on the Ticketmaster platform.

DO NOT CALL this tool if the user:

• Asks general knowledge questions about an artist or band (origin, albums, members, biography, discography)
• Asks general knowledge questions about a venue (address, directions, parking, capacity, seating chart, policies, door times)
• Asks about event details like cast, performers, or who is starring in a show
• Asks about events NOT typically sold on Ticketmaster (local amateur sports, little league, school events, community events, private events)
• Asks for recommendations or opinions (e.g., "best concerts ever")
• Asks any informational question that does not require searching the Ticketmaster event catalog

IMPORTANT: Call this tool ONLY ONCE per user prompt. Do NOT call it a second time to refine, re-sort, or re-format. The single call returns all data needed — format the returned results directly. If the tool returns zero results, do NOT retry with different parameters. Instead, inform the user that no results were found and suggest they try a different search (e.g., expand the date range, change the location, or check the spelling).

CRITICAL

• FIELD USAGE RULES:

attractionKeyword

• ONLY for specific artist/performer/team NAMES:
• IMPORTANT: The attraction needs to be spelled exactly how the artist/performer/team spells it (e.g., "blink-182")
• CORRECT: "Taylor Swift", "Lakers", "Beyonce", "Coldplay", "Chicago Bulls"
• WRONG: "NBA", "NFL", "NHL", "MLB" (these are leagues/classifications, use classificationName)
• WRONG: "rock", "pop", "sports", "comedy" (these are genres, use classificationName)
• WRONG: "Los Angeles", "New York" (these are locations, use location object)
• Leave EMPTY if user asks for a genre/category without naming a specific artist
• IMPORTANT: Use attractionKeyword for individual team names (e.g., "Lakers"), NOT league names (e.g., "NBA")

venueKeyword

• ONLY for specific venue NAMES:
• DO NOT include location object if a specific venue is mentioned - the venue defines the location
• CORRECT: "Madison Square Garden", "Staples Center", "Red Rocks Amphitheatre"
• WRONG: "Los Angeles", "Chicago", "New York" (these are cities, use location object)
• WRONG: "arena", "stadium", "theater" (these are venue types, not names)
• Leave EMPTY if user mentions a city/location without naming a specific venue

eventKeyword

• ONLY for specific event/show/tour NAMES:
• CORRECT: "Eras Tour", "Hamilton", "Lollapalooza", "Coachella"
• WRONG: "rock concert", "sports game" (these are categories, use classificationName)
• Leave EMPTY if user asks for a genre/category without naming a specific event

classificationName

• ONLY when user EXPLICITLY asks for a genre/category:
• ONLY populate if user says words like: "rock", "pop", "sports", "comedy", "concerts", "games"
• DO NOT infer or guess a classification from artist/venue/event names
• When the user mentions a genre, subgenre, style, or specific type of event, you MUST map it to the MOST SPECIFIC matching classification from the discovery-classifications taxonomy.
• NEVER choose a parent category when a more specific child classification exists. Example: If the user says "rock concerts", classificationName MUST be "Rock" (not "Music").
• PRECEDENCE RULE: If a keyword could be BOTH a classification and an attraction (e.g., "NBA", "NFL"), ALWAYS use classificationName, NOT attractionKeyword
• "Taylor Swift" -> attractionKeyword only, NOT classificationName="Pop"
• "Lakers game" -> attractionKeyword="Lakers" only, NOT classificationName="Sports"
• "NBA games" -> classificationName="NBA" ONLY, NOT attractionKeyword="NBA" and NOT classificationName="Basketball"
• "rock concerts in LA" -> classificationName="Rock" (user explicitly said "rock")

location

• ONLY when NO venueKeyword is provided:
• NEVER send location if venueKeyword has a value - the venue defines the location
• Use when user mentions: city names, states, zip codes, "near me", "nearby"
• Provide: latitude, longitude, radius (in miles)
• "events at MSG" -> venueKeyword="Madison Square Garden", location=null
• "events in Los Angeles" -> location={latitude: 34.0522, longitude: -118.2437, radius: 25}

COMMON MISTAKES TO AVOID:

• "Taylor Swift at MSG" -> attractionKeyword="Taylor Swift", venueKeyword="Madison Square Garden", location=null, classificationName=null

NOT: location={NYC coords} or classificationName="Pop"

• "events at Staples Center" -> venueKeyword="Staples Center", location=null

NOT: location={LA coords}

• "Taylor Swift in New York" -> attractionKeyword="Taylor Swift", location={NYC coords}, classificationName=null

NOT: classificationName="Pop" (don't infer genre from artist)

• "NBA games in NY" -> classificationName="NBA", location={NY coords}

NOT: attractionKeyword="NBA" (NBA is a classification, not an attraction) NOT: classificationName="Basketball" (use the most specific classification: "NBA")

• "rock concerts in LA" -> classificationName="Rock", location={LA coords}

NOT: attractionKeyword="rock"

DECISION TREE: 1. Does the keyword match a classification (e.g., "NBA", "NFL", "rock", "pop")? -> classificationName (takes precedence) 2. Is there a specific artist/performer/team name that is NOT a classification? -> attractionKeyword 3. Is there a specific venue name? -> venueKeyword (and SKIP location) 4. Is there a specific event/tour/show name? -> eventKeyword 5. Did user EXPLICITLY mention a genre/category? -> classificationName (don't infer) 6. Is there a city/area mentioned AND no venueKeyword? -> location object 7. Did user EXPLICITLY mention a price? -> prices (format "min,max", e.g. "0,100" for under $100)

DISAMBIGUATION

• MULTIPLE ENTITIES:
• This tool searches for ONE OF EACH PARAMETER: ONE attraction, ONE venue, ONE event name, and ONE classification at a time.
• If the user's prompt mentions MULTIPLE attractions (e.g., "Foo Fighters and Gorillaz events"),

MULTIPLE venues (e.g., "events at MSG and Barclays Center"), MULTIPLE event names (e.g., "Lollapalooza and Coachella"), or MULTIPLE classifications (e.g., "rock and comedy shows"), DO NOT attempt to search for all of them in one call.

• Instead, ask the user which one they'd like to search for first, then proceed with that single search.
• This DOES NOT apply to combining different parameter types (e.g., "Taylor Swift at MSG" is valid —

one attraction + one venue). You can freely combine one of each parameter type in a single search.

OTHER PARAMETERS:

• startDateTime / endDateTime: Date range filter (future dates, ISO 8601 with timezone, e.g. "2025-07-04T00:00:00Z"). endDateTime should be set to +12 hours from the end of the final date in the range to accomodate events which start late into the evening and end the following day.

Translate relative time expressions to concrete date ranges using the current date:

• "this <period>" (today/week/weekend/month): startDateTime = now, endDateTime = end of that period
• "next <period>" (next week/weekend/month): the FULL period AFTER the current one (e.g. next weekend = the Sat/Sun after this coming weekend)
• "tonight"/"today"/"tomorrow" or named days ("this Friday", "on Saturday"): that day 00:00:00–23:59:59
• Named months ("in July"): first to last day of that month
• Relative durations ("next 30 days"): now to N days from now

If the computed date is in the past, advance to the next valid occurrence.

• size: Page size for results
• page: Page number (0-indexed)

KEYWORD CLEANUP (apply before searching):

• Fix typos: "Talyor Swift" -> "Taylor Swift", "Masdison Square Garden" -> "Madison Square Garden"
• Expand acronyms: "MSG" -> "Madison Square Garden", "LA Lakers" -> "Los Angeles Lakers"
• Proper capitalization: "beyonce" -> "Beyonce", "red rocks" -> "Red Rocks"

If no results found, offer to expand date range, change location, or explore similar options. If hasMorePages = true, ask whether to show next page.

SUMMARIZATION:

• If the Ticketmaster widget is available, do not include any URLs or links in your response. Direct the user to interact with the widget to browse events and purchase tickets.
• IMPORTANT: Reference content field in meta response for summarization guideline.