Crawlora MCP

stubhub_carousel

Read-only

Fetch anonymous discovery carousel sections from a StubHub performer page using its performer ID and slug. Use stubhub_performer_events for that performer's schedule, stubhub_trending for featured performers, or stubhub_explore for location-based events.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "performer_slug": "<performer_slug>",
      "performer_id": "<performer_id>",
      "top_level_category_id": "<top_level_category_id>",
      "category_id": "<category_id>",
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "stubhub_carousel"
  }
}

Input Schema

Name	Required	Description
`lat`	Yes	Required. Latitude, -90 to 90.
`lon`	Yes	Required. Longitude, -180 to 180.
`max`	No	Optional. Maximum items per carousel section, 1 to 50. Defaults to 10.
`category_id`	Yes	Required. The performer/category id used by StubHub's carousel request.
`performer_id`	Yes	Required. The performer's numeric id.
`performer_slug`	Yes	Required. The performer's URL slug, obtained from a StubHub performer URL or another endpoint's URL field.
`top_level_category_id`	Yes	Required. One of 1 (Theater), 2 (Sports), or 3 (Concerts), from stubhub-navigation-categories.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the useful 'anonymous' qualifier (no auth/user context needed), but says nothing about return shape, pagination, or the role of the lat/lon inputs, so it adds only modest behavioral context.

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 tight sentences, front-loaded with the core action and followed by routing guidance. No filler and no repetition of schema content.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. The description covers purpose and alternatives, but the surprising required lat/lon and category IDs for a 'performer carousel' are left for the schema to explain, leaving a small gap.

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 the schema fully documents all seven parameters including ranges and defaults. The description names only performer ID and slug and adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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 (Fetch), resource (anonymous discovery carousel sections), and scope (from a StubHub performer page keyed by performer ID and slug). It explicitly names the sibling tools it is not, so an agent can distinguish it without opening schemas.

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 routes the agent to three concrete alternatives with their use cases (stubhub_performer_events for schedule, stubhub_trending for featured performers, stubhub_explore for location-based events). It does not add an explicit 'use this tool when...' clause, but the purpose statement plus the alternatives make the selection condition clear.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?