Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stubhub_carousel

List StubHub performer discovery carousels by performer slug, ID, category, and location to get alternative, recently viewed, maybe-interested, and trending-event sections.

Instructions

List StubHub performer discovery carousels. Returns the performer-page alternative, recently viewed, maybe-interested, and trending-event carousel sections. Obtain performer_slug and performer_id from a real StubHub performer URL or another StubHub result.

Input Schema

NameRequiredDescriptionDefault
latYesLatitude
lonYesLongitude
maxNoMaximum items per carousel section; defaults to 10
category_idYesStubHub category id
performer_idYesStubHub performer numeric id
performer_slugYesStubHub performer URL slug
top_level_category_idYesTop-level category: 1 (Theater), 2 (Sports), or 3 (Concerts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It helpfully discloses what the tool returns (the four carousel section types), which is real behavioral context beyond the schema. It does not mention auth requirements, rate limits, or any mutation/reversibility concerns, though for a read-only listing tool those gaps are modest.

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?

Three sentences, front-loaded with the tool's purpose followed by return contents and prerequisite guidance. Every sentence contributes and there is no filler.

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?

For a 7-parameter tool with 6 required inputs and no output schema or annotations, the description covers purpose, returns, and identifier sourcing, but omits return structure details and any mention of pagination or the max parameter's behavior beyond what the schema states. Adequate but with visible 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 description coverage is 100%, so the baseline is 3. The description adds meaning by explaining the provenance of the required performer_slug and performer_id (from a real performer URL or another StubHub result), which helps an agent supply valid identifiers rather than guessing them.

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 (List) and resource (StubHub performer discovery carousels) and enumerates the concrete sections returned (performer-page alternative, recently viewed, maybe-interested, trending-event). This lets an agent distinguish it from sibling event-listing tools like stubhub_performer_events, though it doesn't explicitly name a sibling.

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 final sentence gives a useful prerequisite — where to source performer_slug and performer_id (a real StubHub performer URL or another StubHub result). However, there is no explicit statement of when to prefer this tool over alternatives such as stubhub_explore or stubhub_performer_events, so usage is only implied.

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