Crawlora MCP

stubhub_trending_events

Read-only

Fetch a paginated global feed of currently trending StubHub events, optionally filtered by category. Use stubhub_trending for trending topics, stubhub_category_events for a category, or stubhub_explore for discovery.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stubhub_trending_events"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Optional. One-based result page. Defaults to 1.
`top_level_category_id`	No	Optional. Filter to one top-level vertical: 0 (all categories, default), 1 (Theater), 2 (Sports), 3 (Concerts).

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.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 the feed is paginated and global (no geo scoping), which is useful context, but it doesn't describe result volume, refresh cadence, or what 'trending' is ranked by. 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 with zero filler. The core capability is front-loaded and the sibling-routing sentence follows immediately; every clause earns its place.

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?

For a read-only, zero-required-parameter feed with full schema coverage, an output schema, and annotations, the description is essentially complete. The only mild gap is not characterizing what 'trending' means or roughly how many results to expect, but that is minor given the structured data available.

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 coverage is 100%, so both parameters are already documented, including the category enum values. The description's 'paginated' and 'optionally filtered by category' merely restate the schema without adding syntax or default details. Baseline 3 when the schema does the heavy lifting.

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 ('paginated global feed of currently trending StubHub events'), including scope ('global') and optional filtering. It explicitly distinguishes itself from three sibling tools by name, so 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?

Gives explicit alternative routing: 'Use stubhub_trending for trending topics, stubhub_category_events for a category, or stubhub_explore for discovery.' The condition selecting each alternative is stated, 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?