Skip to main content
Glama

Performers

performers
Read-onlyIdempotent

Search SeatGeek performers (artists, teams, comedians) by name or genre; returns performer profiles with images, genres, and upcoming event counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoPerformer, team or artist name, e.g. "Taylor Swift".
pageNo1-based page number.
slugNoExact SeatGeek performer slug.
per_pageNoResults per page.
taxonomies.nameNoCategory filter, e.g. nba, concert.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNo
performersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / properties / meta / properties / geolocation / type
      Previous value: -"null"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / performers / items / properties / colors / type
      Previous value: -"null"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / performers / items / properties / divisions / type
      Previous value: -"null"New value: +[
      +  "array",
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / performers / items / properties / home_venue_id / type
      Previous value: -"null"New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / performers / items / properties / location / type
      Previous value: -"null"New value: +[
      +  "object",
      +  "null"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / performers / items / properties / ada_dominant_image_color / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  3. Changed3 schema fields changed
    • changedOutput schema / properties / performers / items / properties / image / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / performers / items / properties / image_attribution / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / performers / items / properties / image_license / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  4. Changed6 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -true
    • 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 / q
      Added value: +{
      +  "description": "Performer, team or artist name, e.g. \"Taylor Swift\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / slug
      Added value: +{
      +  "description": "Exact SeatGeek performer slug.",
      +  "type": "string"
      +}
    • addedInput schema / properties / taxonomies.name
      Added value: +{
      +  "description": "Category filter, e.g. nba, concert.",
      +  "type": "string"
      +}
  5. Changed5 schema fields changed
    • removedOutput schema / properties / count
      Removed value: -{
      -  "description": "Number of items returned.",
      -  "type": "integer"
      -}
    • removedOutput schema / properties / items
      Removed value: -{
      -  "description": "List of performers",
      -  "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"
      +      },
      +      "has_upcoming_events": {
      +        "type": "boolean"
      +      },
      +      "home_venue_id": {
      +        "type": "null"
      +      },
      +      "id": {
      +        "type": "number"
      +      },
      +      "image": {
      +        "type": "string"
      +      },
      +      "image_attribution": {
      +        "type": "string"
      +      },
      +      "image_license": {
      +        "type": "string"
      +      },
      +      "image_rights_message": {
      +        "type": "string"
      +      },
      +      "images": {
      +        "properties": {
      +          "huge": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "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",
      +                "number"
      +              ]
      +            },
      +            "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"
      -]
  6. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds that results include images, genres, and upcoming event counts, which is mildly useful, but it omits pagination behavior, rate limits, or auth requirements. Given the annotation coverage and the existing output schema, a 3 is appropriate.

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, well-structured sentence that front-loads the verb and resource, then lists the return contents. No filler, no repetition, and the most important information (what it searches and what it returns) comes first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations, a 100% schema coverage, and an output schema, the description covers the essentials for a basic search call. However, it is incomplete for routing in a toolset containing 'performer' and 'performer_by_slug', and it says nothing about pagination defaults or result limits. Adequate but with clear gaps.

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 five parameters (q, page, slug, per_page, taxonomies.name) are already documented in the schema. The description only loosely maps 'name or genre' to q and taxonomies.name, adding no syntax or format detail beyond what the schema provides. Baseline 3 applies when the schema carries the parameter burden.

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 ('Search') and resource ('SeatGeek performers') with clarifying examples (artists, teams, comedians) and the search dimensions (name, genre). It is clearly a list/search operation, but it never names or contrasts with the sibling tools 'performer' or 'performer_by_slug', so the agent must infer which of the three to call.

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

Usage Guidelines2/5

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

The description says what can be searched by but offers no when-to-use guidance, no prerequisites, and no mention of the alternatives 'performer' or 'performer_by_slug'. The agent is left to infer that this is the multi-result search endpoint versus the single-entity siblings.

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.