Crawlora MCP

ticketmaster_venue_events

Read-only

Fetch upcoming Ticketmaster event rows at one venue. Use ticketmaster_venue for venue details, ticketmaster_venue_enhanced_details for expanded metadata, or seatgeek_venue_events and stubhub_venue_events to compare other ticket marketplaces.

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": {
      "id": "<id>"
    },
    "name": "ticketmaster_venue_events"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Required. Numeric Ticketmaster venue id.
`page`	No	Optional. Zero-based result page. Defaults to 0.
`sort`	No	Optional. One of relevance, date. Defaults to date.

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

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds a genuine behavioral constraint beyond structured data: results are limited to 'upcoming' events, which tells the agent not to expect historical listings. It does not add auth, rate-limit, or ordering nuance, but against annotations this is solid context.

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 primary purpose is front-loaded, and the sibling routing follows immediately in a single compact clause.

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?

The tool has an output schema, full annotation coverage, and 100% schema description coverage, so the description need not explain returns or parameters. Combined with the explicit sibling routing and the 'upcoming' scoping, an agent has everything needed to call it correctly.

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 id, page, and sort are fully documented in the schema (including defaults and the relevance/date options). The description only implies the venue-id lookup via 'at one venue' and adds no syntax or format detail beyond what the schema already provides, so 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 (upcoming Ticketmaster event rows) scoped to one venue. It explicitly carves out its niche versus ticketmaster_venue and ticketmaster_venue_enhanced_details, so an agent can distinguish it without opening sibling 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?

Names the alternatives explicitly — ticketmaster_venue for details, ticketmaster_venue_enhanced_details for metadata, seatgeek_venue_events and stubhub_venue_events for cross-marketplace comparison — giving clear when-to-use routing. Nothing is left 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?