Seatgeek

Events

events

Read-onlyIdempotent

Search SeatGeek events by keyword, venue, performer, location, date range, or category; returns event listings with name, datetime, venue, performers, and ticket URLs.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Free-text search: performer, team, venue or event name. Put the subject of the question here.
`page`	No	1-based page number.
`sort`	No	e.g. "datetime_utc.asc" (soonest first) or "score.desc" (most popular).
`per_page`	No	Results per page (default 10, max 5000).
`venue.city`	No	City name, e.g. "New York".
`venue.state`	No	2-letter state code, e.g. "NY".
`venue.country`	No	2-letter country code, e.g. "US".
`performers.slug`	No	SeatGeek performer slug (from the performers tool) — exact, unlike q.
`taxonomies.name`	No	Category: concert, sports, theater, music_festival, nba, nfl, mlb, nhl ...
`datetime_utc.gte`	No	Lower bound, e.g. "2026-08-01" or "2026-08-01T00:00:00". Use with .lte for "this month".
`datetime_utc.lte`	No	Upper bound, e.g. "2026-08-31".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`events`	No	List of events

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedAug 1, 2026

removedInput schema / additionalProperties
```
Removed value: -true
```

addedInput schema / properties / datetime_utc.gte

Added value: +{
+  "description": "Lower bound, e.g. \"2026-08-01\" or \"2026-08-01T00:00:00\". Use with .lte for \"this month\".",
+  "type": "string"
+}

addedInput schema / properties / datetime_utc.lte

Added value: +{
+  "description": "Upper bound, e.g. \"2026-08-31\".",
+  "type": "string"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "1-based page number.",
+  "type": "number"
+}

addedInput schema / properties / per_page

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

addedInput schema / properties / performers.slug

Added value: +{
+  "description": "SeatGeek performer slug (from the performers tool) — exact, unlike q.",
+  "type": "string"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "Free-text search: performer, team, venue or event name. Put the subject of the question here.",
+  "type": "string"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "e.g. \"datetime_utc.asc\" (soonest first) or \"score.desc\" (most popular).",
+  "type": "string"
+}

addedInput schema / properties / taxonomies.name

Added value: +{
+  "description": "Category: concert, sports, theater, music_festival, nba, nfl, mlb, nhl ...",
+  "type": "string"
+}

addedInput schema / properties / venue.city

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

addedInput schema / properties / venue.country

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

addedInput schema / properties / venue.state

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

First observedMay 27, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context by listing the return fields, but it does not disclose pagination behavior, default ordering, or any edge cases like how q is fuzzy vs performers.slug exact (the latter is only in the schema). The bar is lowered by annotations, but the description adds only modest behavioral context beyond the safety 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?

The description is a single, front-loaded sentence that efficiently conveys the search dimensions and return type. It is concise, well-structured, and every clause adds value—no filler or redundancy.

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 11 optional parameters, 100% schema coverage, an output schema, and strong annotations, the description is largely sufficient. It covers the primary purpose and capabilities. However, it does not mention default behavior when no filters are provided (e.g., returning popular events) or explicitly note pagination, which are minor gaps for a search tool of this complexity.

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 the schema fully documents each parameter. The description's mention of 'keyword, venue, performer, location, date range, or category' maps to the parameters but adds no new semantics beyond what the schema already says. Baseline 3 is appropriate since the schema already provides detailed parameter meanings and examples.

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 clearly states the tool's function with a specific verb and resource: 'Search SeatGeek events' followed by a list of search dimensions (keyword, venue, performer, location, date range, category). It also mentions the return payload (event listings with name, datetime, venue, performers, ticket URLs), which distinguishes it from the sibling 'event' tool likely used for fetching a single event.

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 provides clear context for when to use the tool: whenever you need to find events matching various criteria. It implies use for search scenarios, but it does not explicitly contrast with the sibling 'event' tool (e.g., 'use events to search, use event to get details by ID'). The plural 'events' and focus on search are implicit differentiators, but explicit exclusions are missing.

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

All Seatgeek 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.