Seatgeek

Venues

venues

Read-onlyIdempotent

Search SeatGeek venues by name, city, state, country, or postal code; returns venue details including address, capacity, and geolocation.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Venue name, e.g. "Madison Square Garden".
`city`	No	City name.
`page`	No	1-based page number.
`state`	No	2-letter state code.
`country`	No	2-letter country code.
`per_page`	No	Results per page.
`postal_code`	No	Postal/ZIP code.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`venues`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedAug 1, 2026

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

addedInput schema / properties / city

Added value: +{
+  "description": "City name.",
+  "type": "string"
+}

addedInput schema / properties / country

Added value: +{
+  "description": "2-letter country code.",
+  "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.",
+  "type": "number"
+}

addedInput schema / properties / postal_code

Added value: +{
+  "description": "Postal/ZIP code.",
+  "type": "string"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "Venue name, e.g. \"Madison Square Garden\".",
+  "type": "string"
+}

addedInput schema / properties / state

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

Changed12 schema fields changedJun 7, 2026
- changedOutput schema / properties / venues / items / properties / address / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / city / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / country / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / display_location / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / extended_address / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / name_v2 / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / postal_code / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / relative_url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / slug / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / state / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / timezone / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / venues / items / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed5 schema fields changedJun 2, 2026

removedOutput schema / properties / count

Removed value: -{
-  "description": "Number of items returned.",
-  "type": "integer"
-}

removedOutput schema / properties / items

Removed value: -{
-  "description": "List of venues",
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / meta

Added value: +{
+  "properties": {
+    "geolocation": {
+      "type": "null"
+    },
+    "page": {
+      "type": "number"
+    },
+    "per_page": {
+      "type": "number"
+    },
+    "took": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / venues

Added value: +{
+  "items": {
+    "properties": {
+      "access_method": {
+        "type": "null"
+      },
+      "address": {
+        "type": "string"
+      },
+      "capacity": {
+        "type": "number"
+      },
+      "city": {
+        "type": "string"
+      },
+      "country": {
+        "type": "string"
+      },
+      "display_location": {
+        "type": "string"
+      },
+      "extended_address": {
+        "type": "string"
+      },
+      "has_upcoming_events": {
+        "type": "boolean"
+      },
+      "id": {
+        "type": "number"
+      },
+      "links": {
+        "items": {},
+        "type": "array"
+      },
+      "location": {
+        "properties": {
+          "lat": {
+            "type": "number"
+          },
+          "lon": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "marquee_city": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "metro_code": {
+        "type": "number"
+      },
+      "name": {
+        "type": "string"
+      },
+      "name_v2": {
+        "type": "string"
+      },
+      "num_upcoming_events": {
+        "type": "number"
+      },
+      "passes": {
+        "items": {
+          "properties": {
+            "image_rights_message": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "pass_type": {
+              "type": "string"
+            },
+            "relative_url": {
+              "type": "string"
+            },
+            "stats": {
+              "properties": {
+                "event_count": {
+                  "type": "number"
+                }
+              },
+              "type": "object"
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "popularity": {
+        "type": "number"
+      },
+      "postal_code": {
+        "type": "string"
+      },
+      "relative_url": {
+        "type": "string"
+      },
+      "score": {
+        "type": "number"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "state": {
+        "type": "string"
+      },
+      "stats": {
+        "properties": {
+          "event_count": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "timezone": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / required

Removed value: -[
-  "items",
-  "count"
-]

First observedMay 27, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds that results include address, capacity, and geolocation, but this is likely covered by the output schema. No additional behavior like pagination details or rate limits is disclosed.

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?

A single, efficient sentence that is front-loaded with the action and resource. No filler or redundant phrasing. Clearly communicates the tool's purpose and key output.

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?

The tool is simple with 100% schema coverage and an output schema, so the description is largely sufficient. However, it doesn't explicitly differentiate from the sibling 'venue' tool, which could lead to confusion. Otherwise, it's complete for a search/read operation.

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 7 parameters are already described in the schema. The description just lists some of these parameters (name, city, state, country, postal code) without adding extra meaning beyond what the schema provides. Baseline 3 applies.

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: searching SeatGeek venues by multiple criteria. It specifies the verb 'Search', the resource 'venues', and the output (details including address, capacity, geolocation). The plural 'venues' naturally distinguishes it from the sibling 'venue' tool.

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

Usage Guidelines3/5

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

The description implies usage for finding venues by location/name but doesn't explicitly discuss when to use this over the singular 'venue' tool or other search alternatives. No exclusions or alternative instructions are provided.

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.