Crawlora MCP

stubhub_performer_events

Read-only

List a known StubHub performer or team's upcoming event records with venue and starting price. Use stubhub_search to find a performer, stubhub_venue_events for a venue calendar, or stubhub_category_events for category-wide 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>"
    },
    "name": "stubhub_performer_events"
  }
}

Input Schema

Name	Required	Description	Default
`performer_id`	Yes	Required. The performer's numeric id, e.g. 6063.
`performer_slug`	Yes	Required. The performer's URL slug, e.g. "kansas-city-chiefs-tickets" from https://www.stubhub.com/kansas-city-chiefs-tickets/performer/6063 -- obtain a real slug+id pair from stubhub-trending's url field.

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

Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, covering the safety profile, and an output schema exists so return shape is handled. The description adds only the 'known performer/team' constraint. No mention of pagination, result caps, or empty-calendar behavior, so it stays at baseline.

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 sentences, no waste, and the routing information is front-loaded right after the purpose statement. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with an output schema and two fully documented required params, the definition covers purpose, scoping, and sibling routing. Nothing an agent needs in order to call it correctly is missing.

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% and the schema itself explains both required params, including that slug+id pairs come from stubhub_trending's url field. The description adds nothing parameter-specific beyond what the schema already provides, so baseline 3 is correct.

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) + resource (a performer's upcoming event records) with scope (venue + starting price), and explicitly distinguishes itself from three siblings (stubhub_search, stubhub_venue_events, stubhub_category_events). An agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names the three alternatives and the condition that selects each: search to find a performer, venue_events for a calendar, category_events for category-wide. This is textbook when-to-use vs alternatives guidance.

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?