Skip to main content
Glama

Get Ticket Listings

get_ticket_listings
Read-only

The tickets on sale for one event on XP: section, row, quantity and the all-in price per ticket in dollars (per_ticket_usd), filterable by quantity, price, section, general admission and parking -- 'cheap seats', 'parking for the game'. event_id comes from search_events, search_market or get_event_details; each listing's uvid is what buy_tickets takes. error_code NO_INVENTORY: the event has nothing listed right now, and retrying will not change that. NO_MATCHING_TICKETS: tickets exist but none fit the filters. EVENT_NOT_FOUND: the event_id is wrong.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ticket_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoAlias for section_tags.
is_gaNoIf true, filter for general admission only.
limitNoMaximum ticket listings to return.
offsetNoPagination offset.
event_idNoEvent identifier from search_events or get_event_details.
order_byNoPrice sort order.
quantityNoNumber of tickets requested.
sectionsNoAlias for section_ids.
api_limitNoBackend limit (advanced; usually omit).
section_idsNoSection IDs filter (list, comma-separated string, or numeric IDs; supports simple ranges like '100-110').
parking_onlyNoIf true, return only parking tickets.
section_tagsNoSection tags filter (e.g. 'Floor', '1xx').
max_price_usdNoMaximum all-in price per ticket in dollars.
min_price_usdNoMinimum all-in price per ticket in dollars.
max_cache_levelNoBackend cache level override (advanced; usually omit).
max_price_centsNoDeprecated, use max_price_usd. Integer cents.
min_price_centsNoDeprecated, use min_price_usd. Integer cents.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / event_id / description
      Previous value: -"Event identifier from search_events or get_event_details. If omitted, the assistant should search/select an event first."New value: +"Event identifier from search_events or get_event_details."
  2. Changed4 schema fields changed
    • changedInput schema / properties / max_price_cents / description
      Previous value: -"Maximum ticket price. Integer cents (20000 = $200.00)."New value: +"Deprecated, use max_price_usd. Integer cents."
    • addedInput schema / properties / max_price_usd
      Added value: +{
      +  "description": "Maximum all-in price per ticket in dollars.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / min_price_cents / description
      Previous value: -"Minimum ticket price. Integer cents (5000 = $50.00)."New value: +"Deprecated, use min_price_usd. Integer cents."
    • addedInput schema / properties / min_price_usd
      Added value: +{
      +  "description": "Minimum all-in price per ticket in dollars.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false, closed world), and the description adds genuinely new behavioral detail: three named error codes with their meaning, plus the key insight that NO_INVENTORY is a terminal state where retrying will not help. It does not cover pagination behavior for the limit/offset pair or ordering semantics beyond the schema's own enum.

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?

A single dense paragraph that front-loads the resource and return fields before the workflow and error codes. The quoted examples ('cheap seats', 'parking for the game') earn their place by mapping user phrasing to filters, though the sentence is long enough that the error-code block could be split for scannability.

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?

With an output schema present, the description need not explain return values, and it still names the price field and units. Combined with full annotation coverage, a complete parameter schema, and explicit error semantics, an agent has everything needed to call this correctly and to interpret failures.

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 all 17 parameters are already documented, including the deprecated cents fields and the alias/advanced params. The description adds only light framing — that price filters are in dollars and that sections/GA/parking are the filter axes — which is already in the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource (tickets on sale for one event) and enumerates the returned fields (section, row, quantity, all-in per-ticket price in dollars). It also names the sibling tools in the pipeline (search_events / search_market / get_event_details feed event_id, buy_tickets consumes uvid), so an agent can place it precisely among siblings.

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?

Gives explicit prerequisites: event_id must come from search_events, search_market or get_event_details, and each returned uvid is the input to buy_tickets — a clear browse-then-buy workflow. It lacks an explicit exclusion (e.g. when to prefer list_open_listings or get_price_history instead), so it stops just short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources