Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stubhub_performer_events

Fetch a StubHub performer or team's upcoming events by slug and numeric ID, returning event names, dates, venues, and starting prices.

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) 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

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.3/5.0
Behavior4/5

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

With no annotations, the description carries full burden and does reasonably well: it discloses the data source (the performer's StubHub page), the returned fields, and importantly the no-results semantics (a zero count with an empty list is a valid no-upcoming-events response). It omits pagination/auth details but covers the operationally important behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then supporting detail. Slightly redundant in restating 'list upcoming events' as 'lists a performer or team's own upcoming schedule', but overall tight and well-structured.

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?

No output schema exists, so the description appropriately enumerates the return fields, and with no annotations it covers the read-only listing nature and the empty-result edge case. Complete enough for an agent to invoke correctly, though pagination/coverage limits are unstated.

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 the baseline is 3, but the description adds genuine meaning by explaining how to derive the slug/id pair from a URL and providing a concrete example. This is more than the schema's terse field descriptions provide.

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?

States a specific verb (List) and resource (a StubHub performer/team's upcoming events), and even enumerates the returned fields (event name, date, venue, starting price). This clearly distinguishes it from venue-based or category-based siblings like stubhub_venue_events.

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?

Gives a concrete prerequisite and source for the required inputs: obtain the performer_slug+performer_id pair from stubhub-trending's url field, with a worked example. It does not explicitly name when NOT to use it versus sibling event tools, but the context is clear enough to select correctly.

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