Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stubhub_venue_events

List a StubHub venue's upcoming events by venue slug and ID, returning event names, dates, and starting prices so you can check its calendar.

Instructions

List a StubHub venue's upcoming events. Lists a venue's own upcoming event calendar (event name, date, starting price) from its StubHub page. Obtain a real venue_slug+venue_id pair from another endpoint's event url field (e.g. https://www.stubhub.com/geha-field-at-arrowhead-stadium-tickets/venue/4467/ -- slug "geha-field-at-arrowhead-stadium-tickets", id 4467). A zero count with an empty events list is a valid no-upcoming-events response.

Input Schema

NameRequiredDescriptionDefault
venue_idYesThe venue's numeric id
venue_slugYesThe venue's URL slug, e.g. geha-field-at-arrowhead-stadium-tickets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations the description carries the full burden, and it does add real context: the returned fields (event name, date, starting price) and the fact that a zero count with an empty list is a valid no-events response. It says nothing about pagination, rate limits, or whether results are cached/live, leaving gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core constraint (venue slug+id) is front-loaded and the example is worth its length, but the first two sentences restate the same idea ('List a StubHub venue's upcoming events' / 'Lists a venue's own upcoming event calendar'), one of which could be cut.

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 2-param read tool with no output schema and no annotations, the description covers what is returned, how to obtain inputs, and the empty-result edge case. Pagination and rate behavior are the only notable omissions, so it is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining how to derive the pair and what the numeric id vs slug look like in a real URL. That is meaningful added semantics over two terse property descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource ('List a StubHub venue's upcoming events') and it implicitly separates itself from stubhub_performer_events by scoping to a venue. It never names a sibling explicitly, so an agent must infer the venue-vs-performer distinction, which holds it back from a 5.

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

Usage Guidelines3/5

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

It gives genuinely useful setup guidance: obtain the venue_slug+venue_id pair from another endpoint's event url field, with a worked example. However it offers no when-to-use or when-not guidance relative to the many sibling venue tools (ticketmaster_venue_events, seatgeek_venue_events), so usage is only partially covered.

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

Deploy Server

Other Tools