Crawlora MCP

stubhub_venue_events

Read-only

List upcoming event rows for a known StubHub venue, including dates and starting prices. Use stubhub_search to discover venues, stubhub_performer_events for one performer's schedule, or stubhub_category_events for events near a location.

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": {
      "venue_slug": "<venue_slug>",
      "venue_id": "<venue_id>"
    },
    "name": "stubhub_venue_events"
  }
}

Input Schema

Name	Required	Description	Default
`venue_id`	Yes	Required. The venue's numeric id, e.g. 4467.
`venue_slug`	Yes	Required. The venue's URL slug, e.g. "geha-field-at-arrowhead-stadium-tickets" from https://www.stubhub.com/geha-field-at-arrowhead-stadium-tickets/venue/4467/ -- obtain a real slug+id pair from another endpoint's event 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 already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds only the 'known venue' prerequisite and a brief note on returned content (dates, starting prices); it says nothing about pagination, auth, or result limits. With annotations carrying the safety profile and an output schema covering the return shape, a 3 is appropriate.

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, zero waste, with the purpose front-loaded and the sibling routing following immediately. 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 simple venue lookup, the description plus 100%-covered schema, read-only/openWorld annotations, and an existing output schema give an agent everything needed to call it correctly. No missing element.

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 documents both params richly, including an example slug/id pair and how to obtain them from another endpoint's event url field. The description adds no parameter detail beyond the schema, so the baseline 3 holds.

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 ('upcoming event rows for a known StubHub venue') plus the content ('dates and starting prices'). It explicitly names the sibling tools it is not, so an agent can distinguish it 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?

Names three alternatives with the exact condition that selects each: stubhub_search to discover venues, stubhub_performer_events for a single performer's schedule, stubhub_category_events for location-based events. This is explicit when-to-use-which routing, leaving nothing to inference.

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?