Seatgeek

Performer By Slug

performer_by_slug

Read-onlyIdempotent

Look up a SeatGeek performer profile by URL slug (e.g. "taylor-swift"); returns the same performer detail as the performer tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`performers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 30, 2026

removedOutput schema / properties / count

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

removedOutput schema / properties / items

Removed value: -{
-  "description": "Performer matching slug",
-  "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 / performers

Added value: +{
+  "items": {
+    "properties": {
+      "ada_dominant_image_color": {
+        "type": "string"
+      },
+      "colors": {
+        "type": "null"
+      },
+      "divisions": {
+        "type": "null"
+      },
+      "domain_information": {
+        "items": {},
+        "type": "array"
+      },
+      "genres": {
+        "items": {
+          "properties": {
+            "id": {
+              "type": "number"
+            },
+            "name": {
+              "type": "string"
+            },
+            "primary": {
+              "type": "boolean"
+            },
+            "slug": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "has_upcoming_events": {
+        "type": "boolean"
+      },
+      "hidden": {
+        "type": "boolean"
+      },
+      "home_venue_id": {
+        "type": "null"
+      },
+      "id": {
+        "type": "number"
+      },
+      "is_event": {
+        "type": "boolean"
+      },
+      "links": {
+        "items": {},
+        "type": "array"
+      },
+      "location": {
+        "type": "null"
+      },
+      "name": {
+        "type": "string"
+      },
+      "num_upcoming_events": {
+        "type": "number"
+      },
+      "popularity": {
+        "type": "number"
+      },
+      "primary": {
+        "type": "boolean"
+      },
+      "relative_url": {
+        "type": "string"
+      },
+      "score": {
+        "type": "number"
+      },
+      "short_name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "stats": {
+        "properties": {
+          "event_count": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "taxonomies": {
+        "items": {
+          "properties": {
+            "id": {
+              "type": "number"
+            },
+            "name": {
+              "type": "string"
+            },
+            "parent_id": {
+              "type": "null"
+            },
+            "rank": {
+              "type": "number"
+            },
+            "seo_event_type": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "type": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "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 well covered. The description adds only that the response matches the 'performer' tool's detail, which is modest added context beyond what annotations provide.

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 with the lookup action, the input format, and a concrete example. 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?

An output schema exists, so return values need not be explained, and the sole required parameter is characterized. Sufficient for an agent to call it correctly; only the routing versus the 'performer' sibling remains ambiguous.

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?

Schema coverage is 0%, but there is only one parameter and the description carries its semantics — it is a URL slug — reinforced by the 'taylor-swift' example format. That is genuinely useful beyond the bare string type in the schema.

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 — 'Look up a SeatGeek performer profile by URL slug' — and anchors it with the 'taylor-swift' example. It references the sibling 'performer' tool but frames the difference as input format rather than clearly stating when each should be chosen, so it falls short of full sibling differentiation.

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 mention of the 'performer tool' hints at an alternative and implies this should be used when you have a slug, but it never states the condition explicitly (e.g. 'use when you have a slug instead of an ID'). Usage is implied rather than spelled out.

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.