Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ticketmaster_discover_city_events

List events for a Ticketmaster discover city by city slug and country code; returns paginated details like title, start time, venue, attractions, and status flags.

Instructions

List events in a Ticketmaster discover city. Lists events for a Ticketmaster discover city, identified by city (a slug from ticketmaster-discover-cities) and country (two-letter code matching the city, default US). It covers all municipalities grouped under that destination. page is zero-based, 0 to 49. Each event has title, start time, venue, attractions and status flags.

Input Schema

NameRequiredDescriptionDefault
cityYesTicketmaster discover city slug
pageNoZero-based page
countryNoTwo-letter country code matching the selected city

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

There are no annotations, so the description must carry the behavioral burden. It discloses that the tool lists events, covers all municipalities grouped under the destination, uses zero-based pages with a 0–49 range, and returns event titles, start times, venues, attractions, and status flags. It does not mention ordering, rate limits, or error behavior, but it provides substantial context for a read-only listing.

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?

The description is front-loaded and compact, with the core purpose stated first and parameter details following. The opening two sentences are slightly redundant ('List events in a Ticketmaster discover city. Lists events for...'), but overall it is efficient.

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?

The tool is simple, the input schema is fully described, and there is no output schema. The description reasonably compensates by naming the event fields returned and explaining the pagination range and country default. It is complete enough for correct invocation, though adding ordering or result-limit context would improve it.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema by identifying the source of the city slug, clarifying that country is a two-letter code matching the selected city with default US, and specifying the page range is 0 to 49.

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?

The description states a specific verb and resource: listing events in a Ticketmaster discover city. It is clear about the scope (all municipalities grouped under that destination), but it does not explicitly differentiate itself from sibling tools like ticketmaster_discover_category_events or ticketmaster_search_events.

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?

The description implies usage by specifying that city must be a slug from ticketmaster-discover-cities and that country should match the city. However, it gives no explicit guidance on when to choose this tool over similar siblings such as ticketmaster_search_events or ticketmaster_discover_category_events.

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