Seatgeek

Taxonomies

taxonomies

Read-onlyIdempotent

List all SeatGeek event taxonomies (sports, concerts, theater, etc.) with their IDs and parent/child hierarchy; useful for filtering events by category.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`taxonomies`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026
- changedOutput schema / properties / taxonomies / items / properties / short_name / 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 taxonomies",
-  "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 / taxonomies

Added value: +{
+  "items": {
+    "properties": {
+      "id": {
+        "type": "number"
+      },
+      "image": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "images": {
+        "properties": {
+          "huge": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "is_visible": {
+        "type": "boolean"
+      },
+      "name": {
+        "type": "string"
+      },
+      "parent_id": {
+        "type": [
+          "null",
+          "number"
+        ]
+      },
+      "rank": {
+        "type": "number"
+      },
+      "seo_event_type": {
+        "type": "string"
+      },
+      "short_name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "stats": {
+        "properties": {
+          "event_count": {
+            "type": "number"
+          },
+          "next_event_datetime_utc": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "performer_count": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / required

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

First observedMay 27, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful shape information (IDs plus parent/child hierarchy) but nothing beyond that, which is appropriate for a no-argument read tool.

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 front-loaded sentence pairing the primary action with the reason to call it; every clause earns its place and there is 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?

For a zero-argument lister with an output schema already present, the description is essentially complete: it says what is returned (IDs and hierarchy) and why. Only the absence of explicit routing guidance to sibling tools keeps it short of a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the 4 baseline applies; there is no argument syntax for the description to document and it correctly does not invent any.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list SeatGeek event taxonomies) with illustrative examples of the taxonomy types and the hierarchy they carry. This clearly distinguishes it from siblings like events, event, performers, and venues, though it does not explicitly name any sibling it is not.

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 closing clause 'useful for filtering events by category' implies the context in which an agent should reach for this tool, but it gives no explicit when-not guidance and never names an alternative sibling such as events.

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.