Crawlora MCP

stubhub_category_events

Read-only

Fetch paginated StubHub events for a category with venue, distance, date, and ticket availability. Use stubhub_search to find events or stubhub_performer_events and stubhub_venue_events to scope to a performer or venue.

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": {
      "category_id": "<category_id>",
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "stubhub_category_events"
  }
}

Input Schema

Name	Required	Description
`to`	No	Optional. End of the date range, same accepted formats as from. Defaults to 14 days after from.
`lat`	Yes	Required. Latitude, -90 to 90 -- results and distances are location-dependent.
`lon`	Yes	Required. Longitude, -180 to 180.
`from`	No	Optional. Start of the date range: RFC3339 or a bare date (2026-09-15). Defaults to now.
`page`	No	Optional. One-based result page. Defaults to 1.
`category_id`	Yes	Required. A category id from stubhub-categories (e.g. a sport league or a top-level vertical).
`radius_miles`	No	Optional. Search radius in miles from lat/lon, 1 to 500. Defaults to 50.
`include_parking_passes`	No	Optional. When true, also includes parking-pass-only listings (name prefixed "PARKING PASSES ONLY") alongside regular event listings. Defaults to false (regular events only).

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 7, 2026

TDQS

A4.2/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 safety profile is covered. The description adds that results are paginated and filterable by venue/distance/date/availability, which is useful, but omits anything about rate limits, auth requirements, or result ordering. With annotations carrying the safety burden, 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 filler. The capability statement is front-loaded and the routing guidance follows immediately.

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 the description plus the fully-covered schema plus annotations give an agent enough to call the tool correctly. Slightly short of 5 only because pagination behavior (page size, total counts) is mentioned but not elaborated.

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 already documents all eight parameters including defaults and formats. The description's list of dimensions (venue, distance, date, availability) is a loose restatement and adds no syntax or default detail beyond the schema. 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) and resource (StubHub events), scoped to a category, and enumerates the differentiating dimensions (venue, distance, date, ticket availability). It also 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 Guidelines5/5

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

Explicitly routes the agent: use stubhub_search to find events, or stubhub_performer_events / stubhub_venue_events to scope to a performer or venue. This is exactly the when-to-use-this-vs-alternatives guidance the dimension asks for.

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.