Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stubhub_performer_events

Get a performer or team's upcoming StubHub events by providing their slug and ID. Returns event name, date, venue, and starting price, with an empty list if none are scheduled.

Instructions

List a StubHub performer or team's upcoming events. Lists a performer or team's own upcoming schedule (event name, date, venue, starting price) scraped from their StubHub page. Obtain a real performer_slug+performer_id pair from stubhub-trending's url field (e.g. https://www.stubhub.com/kansas-city-chiefs-tickets/performer/6063 -- slug "kansas-city-chiefs-tickets", id 6063). A zero count with an empty events list is a valid no-upcoming-events response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
performer_idYesThe performer's numeric id
performer_slugYesThe performer's URL slug, e.g. kansas-city-chiefs-tickets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the output contents and explicitly handles the edge case of no upcoming events ('zero count with empty events list'), which is valuable. It does not mention pagination, rate limits, or read-only nature, but for a simple list tool these are less critical.

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?

The description is two sentences with no redundancy. The core purpose and output are front-loaded, followed by parameter sourcing and an edge-case note. Every sentence earns its place.

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 tool with two simple parameters and no output schema, the description adequately covers purpose, output fields, parameter sourcing, and the empty response case. It does not discuss pagination or auth, but these are unlikely to be blockers for this kind of list operation.

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 schema covers both parameters at 100%, so baseline is 3. The description adds meaningful context by explaining how to obtain a valid slug+id pair from stubhub-trending and provides a concrete URL example, going beyond the schema's basic descriptions.

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 purpose: listing a StubHub performer or team's upcoming events. It specifies the output fields (event name, date, venue, starting price) and distinguishes from sibling tools like venue-based or search tools by focusing on a specific performer/team identified by slug+id.

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

Usage Guidelines4/5

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

It provides concrete guidance on sourcing the required parameters from stubhub-trending's URL, establishing a clear workflow. However, it does not explicitly contrast with alternatives like stubhub_venue_events or stubhub_search, so the 'when not to use' is implicit rather than explicit.

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