Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ticketmaster_venue_events

Fetch upcoming Ticketmaster events at a venue by numeric ID, with page and sort controls for date or relevance.

Instructions

List a venue's Ticketmaster events. Lists upcoming Ticketmaster events at the venue with numeric id. page is zero-based, 0 to 49, default 0; sort is relevance or date (default). Each event has title, start time, time zone, attractions, presales, seat map and status flags such as sold_out and cancelled. The response gives total.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Ticketmaster venue id
pageNoZero-based page (0-49)
sortNoResult order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "date"
+]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

No annotations, so the description carries the full burden. It discloses the pagination cap (page 0-49, default 0), the sort options and default, the per-event fields returned (title, start time, time zone, attractions, presales, seat map, sold_out/cancelled flags) and that the response carries a total. Auth/rate-limit behavior is not covered, but the behavioral profile for a read-only listing is well conveyed.

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

Conciseness4/5

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

Front-loaded with the core action, then parameters, then return shape. Slightly redundant opening ('List a venue's Ticketmaster events. Lists upcoming Ticketmaster events at the venue') but otherwise dense and waste-free.

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 3-param, read-only list tool with no output schema and no annotations, the description covers inputs, defaults, paging limits and the returned event shape including total. Missing sibling disambiguation and auth notes keep it short of 5.

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%, but the description adds value the schema lacks: the default for page (0) and that sort defaults to date, plus the 0-49 bound and what the id refers to. This goes beyond restating the schema, so above the baseline 3.

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 venue's Ticketmaster events... upcoming events at the venue with numeric id'. An agent can tell this retrieves venue-scoped events. It does not distinguish itself from very similar siblings (stubhub_venue_events, seatgeek_venue_events, ticketmaster_attraction_events), so not 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?

Usage is implied by 'a venue's events' and the required venue id, but there is no explicit when-to-use or when-not, and no routing to/from ticketmaster_venue or ticketmaster_attraction_events. Adequate but leaves sibling selection to inference.

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