Skip to main content
Glama

Ticker: Live Event Ticket Market

Search Events

search_events
Read-only

Finds ticketed events by name, performer, venue or date, and by on-sale, presale or added dates, and returns their event ids. Use it when the person names an event, act or venue, or when a later call needs an event id. It also lists events a page at a time by category, venue capacity, primary tickets left, TM resale get-in, resale-to-primary or completed sales. To filter or rank events by any other price, demand or inventory number, use screen_events. Rows from other tools already carry event_id and event_url, so a second search for the same event is not needed.

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": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe page to read, from 1. Default 1.
limitNoRows per page. A page too large for one tool result comes back as the first rows plus `meta.truncated` and `meta.total_rows`; narrow the search or the dates rather than repeating the call.
queryNoAlias for `search`; prefer `search`. Ignored when `search` is also present.
searchNoRanking words (hottest, best, top, movers) are a sort on screen_events, never search text. NOT A LINK RESOLVER: rows from other tools already carry `event_id` and `event_url`; matching a row by name can land on a different event. A marketplace event link or id is not search text either: pass it as `event_id` to an event tool. Names only: event, performer or venue (min 2 chars), e.g. "taylor swift", "lakers", "Madison Square Garden". Words match in any order: each word of 3 or more letters must be in the event's name, its performer or its venue, so "Red Sox Yankees" finds the game. Joining words (vs, and, the) are ignored. Rows whose name holds every word come first, and inside each group the events Ticker covers most closely, then the soonest. Not a ranking word (hottest, best, top, movers) and not a typo of one. A venue term returns the events playing there. Venues are stored under their official name, so expand a nickname ("MSG") before searching. Omit to browse by filters alone; use screen_events to rank.
statusNoFilter by event status. Default 'active', the live universe. When the first page of a search with text finds nothing it is re-run over every status and the result says retried_including_inactive: true; each row carries currently_priced (false = the event exists but is not priced right now).active
date_toNoEvent date on/before this instant (ISO 8601, offset ok, over utc_date).
parkingNoParking events: a parking pass that is its own event (sub_category_id 75 or 'Parking' in the name). `hide` (the default) leaves them out; `only` returns parking alone; `include` returns parking beside every other event. Set `only` when the user asks for parking, `include` when they want both; leave it at `hide` otherwise. Under hide a search for 'parking' by name still finds parking.hide
sort_byNoSort key. Default utc_date; with search text and no sort_by, the closest name matches come first. Sorting by onsale_date or presale1_date keeps the events where that date is known (only a minority carry sale dates). sold_24h keeps the events with a completed sale in the last 24 hours, most first.
venue_idNoRestrict to one venue. Ticker venue id, `vn` plus ten characters. A marketplace id also resolves with its `vs:` prefix, and bare until 2027-09-13.
date_fromNoEvent date on/after this instant (ISO 8601, offset ok, over utc_date).
onsale_toNoPublic on-sale on/before this instant. Events with no known on-sale date are excluded.
created_toNoTicker discovered the event on/before this instant.
presale_toNoFirst presale on/before this instant. Events with no known presale date are excluded.
sort_orderNoDefault asc (soonest first), the natural discovery order; for sold_24h desc (most first).
category_idNoOnly this category.
onsale_fromNoPublic on-sale on/after this instant. Events with no known on-sale date are excluded.
sold_1d_minNoAt least this many completed sales in the last day.
sold_3d_minNoAt least this many completed sales in the last 3 days.
sold_7d_minNoAt least this many completed sales in the last 7 days.
capacity_maxNoThe venue's seats, at most this.
capacity_minNoThe venue's seats, at least this.
created_fromNoTicker discovered the event on/after this instant.
include_pastNoInclude events whose date is already past. Default false (upcoming only). When true without an explicit date_from, results are bounded to the last 90 days.
performer_idNoRestrict to events headlined by one performer. Ticker performer id, `pf` plus ten characters, as returned by every tool here. A marketplace id also resolves with its `vs:` prefix, and bare until 2027-09-13.
presale_fromNoFirst presale on/after this instant. Events with no known presale date are excluded.
presale_scopeNoMatch the presale range against the first presale (default) or any named presale.
tmr_get_in_maxNoThe lowest all-in price on TM resale, in dollars, at most this.
tmr_get_in_minNoThe lowest all-in price on TM resale, in dollars, at least this.
primary_left_maxNoPrimary tickets still on sale, at most this.
primary_left_minNoPrimary tickets still on sale, at least this.
primary_sold_maxNoPercent of the primary house taken, 0 to 100, at most this.
primary_sold_minNoPercent of the primary house taken, 0 to 100, at least this.
monitoring_priorityNoFilter by exact coverage tier (1=high … 10=low).
resale_to_primary_maxNoThe resale get-in divided by the primary get-in, all-in, at most this.
resale_to_primary_minNoThe resale get-in divided by the primary get-in, all-in, at least this.
monitoring_priority_maxNoCoverage tier, at most this (1=high, 10=low).
monitoring_priority_minNoCoverage tier, at least this (1=high, 10=low).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changed
    • addedInput schema / properties / capacity_max
      Added value: +{
      +  "description": "The venue's seats, at most this.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / capacity_min
      Added value: +{
      +  "description": "The venue's seats, at least this.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / category_id
      Added value: +{
      +  "description": "Only this category.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / monitoring_priority_max
      Added value: +{
      +  "description": "Coverage tier, at most this (1=high, 10=low).",
      +  "maximum": 10,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / monitoring_priority_min
      Added value: +{
      +  "description": "Coverage tier, at least this (1=high, 10=low).",
      +  "maximum": 10,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / primary_left_max
      Added value: +{
      +  "description": "Primary tickets still on sale, at most this.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / primary_left_min
      Added value: +{
      +  "description": "Primary tickets still on sale, at least this.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / primary_sold_max
      Added value: +{
      +  "description": "Percent of the primary house taken, 0 to 100, at most this.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / primary_sold_min
      Added value: +{
      +  "description": "Percent of the primary house taken, 0 to 100, at least this.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / resale_to_primary_max
      Added value: +{
      +  "description": "The resale get-in divided by the primary get-in, all-in, at most this.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / resale_to_primary_min
      Added value: +{
      +  "description": "The resale get-in divided by the primary get-in, all-in, at least this.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / sold_1d_min
      Added value: +{
      +  "description": "At least this many completed sales in the last day.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / sold_3d_min
      Added value: +{
      +  "description": "At least this many completed sales in the last 3 days.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / sold_7d_min
      Added value: +{
      +  "description": "At least this many completed sales in the last 7 days.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / sort_by / default
      Removed value: -"utc_date"
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort key. Sorting by onsale_date or presale1_date implicitly filters to events where that date is known (only a minority carry sale dates). Default utc_date."New value: +"Sort key. Default utc_date; with search text and no sort_by, the closest name matches come first. Sorting by onsale_date or presale1_date keeps the events where that date is known (only a minority carry sale dates). sold_24h keeps the events with a completed sale in the last 24 hours, most first."
    • changedInput schema / properties / sort_by / enum
      Previous value: -[
      -  "local_date",
      -  "utc_date",
      -  "event_name",
      -  "status",
      -  "monitoring_priority",
      -  "onsale_date",
      -  "presale1_date",
      -  "created_at"
      -]New value: +[
      +  "local_date",
      +  "utc_date",
      +  "event_name",
      +  "status",
      +  "monitoring_priority",
      +  "onsale_date",
      +  "presale1_date",
      +  "created_at",
      +  "sold_24h"
      +]
    • removedInput schema / properties / sort_order / default
      Removed value: -"asc"
    • changedInput schema / properties / sort_order / description
      Previous value: -"Default asc (soonest first), the natural discovery order. The REST endpoint defaults to desc; this tool flips it."New value: +"Default asc (soonest first), the natural discovery order; for sold_24h desc (most first)."
    • addedInput schema / properties / tmr_get_in_max
      Added value: +{
      +  "description": "The lowest all-in price on TM resale, in dollars, at most this.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / tmr_get_in_min
      Added value: +{
      +  "description": "The lowest all-in price on TM resale, in dollars, at least this.",
      +  "minimum": 0,
      +  "type": "number"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / parking
      Added value: +{
      +  "default": "hide",
      +  "description": "Parking events: a parking pass that is its own event (sub_category_id 75 or 'Parking' in the name). `hide` (the default) leaves them out; `only` returns parking alone; `include` returns parking beside every other event. Set `only` when the user asks for parking, `include` when they want both; leave it at `hide` otherwise. Under hide a search for 'parking' by name still finds parking.",
      +  "enum": [
      +    "hide",
      +    "include",
      +    "only"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / page / description
      Added value: +"The page to read, from 1. Default 1."
  4. Changed3 schema fields changed
    • changedInput schema / properties / search / description
      Previous value: -"Ranking words (hottest, best, top, movers) are a sort on screen_events, never search text. NOT A LINK RESOLVER: rows from other tools already carry `event_id` and `event_url`; matching a row by name can land on a different event. A marketplace event link or id is not search text either: pass it as `event_id` to an event tool. Names only: event, performer or venue (min 2 chars), e.g. \"taylor swift\", \"lakers\", \"Madison Square Garden\". Words match in any order: each word of 3 or more letters must be in the event's name, its performer or its venue, so \"Red Sox Yankees\" finds the game. Joining words (vs, and, the) are ignored. Rows whose name holds every word come first. Not a ranking word (hottest, best, top, movers) and not a typo of one. A venue term returns the events playing there. Venues are stored under their official name, so expand a nickname (\"MSG\") before searching. Omit to browse by filters alone; use screen_events to rank."New value: +"Ranking words (hottest, best, top, movers) are a sort on screen_events, never search text. NOT A LINK RESOLVER: rows from other tools already carry `event_id` and `event_url`; matching a row by name can land on a different event. A marketplace event link or id is not search text either: pass it as `event_id` to an event tool. Names only: event, performer or venue (min 2 chars), e.g. \"taylor swift\", \"lakers\", \"Madison Square Garden\". Words match in any order: each word of 3 or more letters must be in the event's name, its performer or its venue, so \"Red Sox Yankees\" finds the game. Joining words (vs, and, the) are ignored. Rows whose name holds every word come first, and inside each group the events Ticker covers most closely, then the soonest. Not a ranking word (hottest, best, top, movers) and not a typo of one. A venue term returns the events playing there. Venues are stored under their official name, so expand a nickname (\"MSG\") before searching. Omit to browse by filters alone; use screen_events to rank."
    • addedInput schema / properties / status / default
      Added value: +"active"
    • changedInput schema / properties / status / description
      Previous value: -"Filter by event status. Omit for all statuses; pass 'active' for the live universe. When a filtered search finds nothing it is re-run over every status and the result says retried_including_inactive: true; each row carries currently_priced (false = the event exists but is not priced right now). 'active' for the live universe."New value: +"Filter by event status. Default 'active', the live universe. When the first page of a search with text finds nothing it is re-run over every status and the result says retried_including_inactive: true; each row carries currently_priced (false = the event exists but is not priced right now)."
  5. Changed1 schema field changed
    • addedInput schema / properties / presale_scope
      Added value: +{
      +  "description": "Match the presale range against the first presale (default) or any named presale.",
      +  "enum": [
      +    "first",
      +    "any"
      +  ],
      +  "type": "string"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / search / description
      Previous value: -"Ranking words (hottest, best, top, movers) are a sort on screen_events, never search text. NOT A LINK RESOLVER: rows from other tools already carry `event_id` and `event_url`; matching a row by name can land on a different event. Names only: event, performer or venue (min 2 chars), e.g. \"taylor swift\", \"lakers\", \"Madison Square Garden\". Words match in any order: each word of 3 or more letters must be in the event's name, its performer or its venue, so \"Red Sox Yankees\" finds the game. Joining words (vs, and, the) are ignored. Rows whose name holds every word come first. Not a ranking word (hottest, best, top, movers) and not a typo of one. A venue term returns the events playing there. Venues are stored under their official name, so expand a nickname (\"MSG\") before searching. Omit to browse by filters alone; use screen_events to rank."New value: +"Ranking words (hottest, best, top, movers) are a sort on screen_events, never search text. NOT A LINK RESOLVER: rows from other tools already carry `event_id` and `event_url`; matching a row by name can land on a different event. A marketplace event link or id is not search text either: pass it as `event_id` to an event tool. Names only: event, performer or venue (min 2 chars), e.g. \"taylor swift\", \"lakers\", \"Madison Square Garden\". Words match in any order: each word of 3 or more letters must be in the event's name, its performer or its venue, so \"Red Sox Yankees\" finds the game. Joining words (vs, and, the) are ignored. Rows whose name holds every word come first. Not a ranking word (hottest, best, top, movers) and not a typo of one. A venue term returns the events playing there. Venues are stored under their official name, so expand a nickname (\"MSG\") before searching. Omit to browse by filters alone; use screen_events to rank."
  7. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Rows per page. A page too large for one tool result comes back as the first rows plus `meta.truncated` and `meta.total_rows`; narrow the search or the dates rather than repeating the call."
    • changedInput schema / properties / search / description
      Previous value: -"Names only: event, performer or venue (min 2 chars), e.g. \"taylor swift\", \"lakers\", \"Madison Square Garden\". Words match in any order: each word of 3 or more letters must be in the event's name, its performer or its venue, so \"Red Sox Yankees\" finds the game. Joining words (vs, and, the) are ignored. Rows whose name holds every word come first. Not a ranking word (hottest, best, top, movers) and not a typo of one. A venue term returns the events playing there. Venues are stored under their official name, so expand a nickname (\"MSG\") before searching. Omit to browse by filters alone; use screen_events to rank."New value: +"Ranking words (hottest, best, top, movers) are a sort on screen_events, never search text. NOT A LINK RESOLVER: rows from other tools already carry `event_id` and `event_url`; matching a row by name can land on a different event. Names only: event, performer or venue (min 2 chars), e.g. \"taylor swift\", \"lakers\", \"Madison Square Garden\". Words match in any order: each word of 3 or more letters must be in the event's name, its performer or its venue, so \"Red Sox Yankees\" finds the game. Joining words (vs, and, the) are ignored. Rows whose name holds every word come first. Not a ranking word (hottest, best, top, movers) and not a typo of one. A venue term returns the events playing there. Venues are stored under their official name, so expand a nickname (\"MSG\") before searching. Omit to browse by filters alone; use screen_events to rank."
  8. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -100
  9. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Alias for `search` — prefer `search`. Ignored when `search` is also present."New value: +"Alias for `search`; prefer `search`. Ignored when `search` is also present."
    • changedInput schema / properties / sort_order / description
      Previous value: -"Default asc (soonest first) — the natural discovery order. The REST endpoint defaults to desc; this tool flips it."New value: +"Default asc (soonest first), the natural discovery order. The REST endpoint defaults to desc; this tool flips it."
  10. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered and the description adds the retrieval behavior: id-only returns, proximity-based ordering of name matches, the browse-without-text mode, and the cross-tool id reuse rule. It does not discuss auth, rate limits, or latency, but for a read-only search that is a minor gap rather than a blocker.

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?

Front-loads what the tool returns and when to call it, then adds the alternative and the id-reuse caveat. The middle sentence enumerating filter families is dense and slightly cumbersome, but every sentence carries usable information with 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?

With 37 optional parameters and no output schema, the description does enough: it names the returned field (event ids), points to event_id/event_url already present in other tools' rows, describes ordering behavior, and routes ranking/filtering elsewhere. It stops short of explaining what a returned row contains beyond the id, which is the remaining 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 description coverage is 100% and the schema text itself carries most of the operational detail (truncation, search word handling, parking semantics, sort defaults), so the description largely restates it. It does add a small amount of framing by grouping the filter families (category, capacity, primary left, resale get-in, resale-to-primary, sold), which is why it is a solid baseline 3 rather than lower.

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 ("finds ticketed events by name, performer, venue or date") and names the return value ("returns their event ids"). It explicitly separates itself from screen_events, so an agent can choose between them without opening either schema.

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?

Gives concrete when-to-use triggers ("when the person names an event, act or venue, or when a later call needs an event id"), an explicit when-not plus alternative ("To filter or rank events by any other price, demand or inventory number, use screen_events"), and a warning that a repeat search is unnecessary because rows from other tools carry event_id and event_url.

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