Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

seatgeek_performer_events

Fetch a SeatGeek performer's upcoming events by numeric performer ID, returning paginated results soonest first. Use it to check schedules for teams, artists, or shows.

Instructions

Get a SeatGeek performer's event schedule. Returns one page of a SeatGeek performer's (sports team, artist, or show) upcoming event schedule, soonest first. performer_id is SeatGeek's own numeric performer id, obtained from a search result (e.g. 1 for the Los Angeles Dodgers).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number
per_pageNoResults per page, 1-50
performer_idYesSeatGeek's own numeric performer id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that only one page is returned, that events are upcoming, and that results are sorted soonest first. It does not mention error handling or rate limits, but covers the key behavioral traits for a read-only getter.

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?

Two concise, front-loaded sentences with no wasted words. The purpose is stated immediately, and the crucial parameter clarification follows without redundancy.

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?

The description covers the essential purpose, key parameter provenance, and pagination behavior<!-- -->. However, with no output schema and no mention of return structure or error cases, the agent cannot fully anticipate what the tool returns or handle failures, leaving noticeable gaps.

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 100%, so baseline is 3. The description adds meaning for performer_id by explaining it is SeatGeek's numeric ID, obtained from a search result, with a concrete example (1 for LA Dodgers). This exceeds baseline, though page and per_page are only described in the schema.

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 a specific verb and resource: 'Get a SeatGeek performer's event schedule.' It distinguishes itself from siblings like seatgeek_venue_events by focusing on performers, and adds helpful detail about the sort order and scope (upcoming events, soonest first).

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 context by noting that performer_id comes from a search result, which hints at using seatgeek_search first. However, it does not explicitly name alternative tools or provide when-to-use/when-not-to-use guidance, leaving the agent to infer the prerequisite.

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

Deploy Server

Other Tools