Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ticketmaster_venue

Fetch a Ticketmaster venue by numeric ID to return its name, address, city, coordinates, time zone, image, URL, and visitor details.

Instructions

Get a Ticketmaster venue. Returns one Ticketmaster venue by numeric id: name, address, city, state, country, postal code, coordinates, time zone, image, URL and visitor information as name and text entries. seat_maps and city_categories are omitted when none exist. An unknown venue returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Ticketmaster venue id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it enumerates the returned fields, discloses that `seat_maps` and `city_categories` are omitted when absent, and states that an unknown venue returns 404. It does not cover auth requirements or rate limits, so it stops short of a 5.

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 purpose, then return contents, then edge-case behavior — a sensible ordering. The field enumeration is a bit listy but every element (omitted fields, 404) earns its place for a tool with no output schema.

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 single-parameter getter with no output schema and no annotations, the description covers return shape, omission behavior, and error behavior, which is what an agent needs. It is not fully complete only because it omits how to obtain the venue id and does not contrast with the enhanced-details sibling.

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% and there is only one parameter, so the schema already documents `id` as a 'Numeric Ticketmaster venue id'. The description's 'by numeric `id`' adds marginal emphasis but no format, range, or sourcing guidance beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Get a Ticketmaster venue') and pins the lookup key ('by numeric `id`'), so an agent can tell it apart from list-oriented siblings like ticketmaster_venue_events. It does not explicitly differentiate itself from ticketmaster_venue_enhanced_details, which is the main missing cue.

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: you need a numeric venue id to call it. There is no explicit when-to-use/when-not guidance, no mention of the enhanced-details alternative, and no note that ids come from search/discovery tools. Adequate but leaves the routing decision 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