Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ticketmaster_discover_cities

List Ticketmaster discover city destinations by two-letter country code and paginate results, returning slugs to fetch local events.

Instructions

List Ticketmaster discover cities. Lists Ticketmaster's discover city destinations for a country (two-letter code, default US). Each city has a slug, name, canonical URL, locale and image. page starts at 1 and per_page runs 1 to 100. The response gives total. Pass a city slug to ticketmaster-discover-city-events.

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page
countryNoTwo-letter country code
per_pageNoCities per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it enumerates returned fields (slug, name, canonical URL, locale, image), states pagination bounds and one-based indexing, and notes the response exposes total. It does not describe rate limits or auth, but for a read-only list endpoint this is solid disclosure.

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 and information-dense, but the opening sentence 'List Ticketmaster discover cities' is immediately restated by 'Lists Ticketmaster's discover city destinations', a minor redundancy that costs a point.

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?

No output schema exists, so listing the returned fields and the total/pagination behavior is exactly what's needed; the routing hint to the city-events sibling rounds it out. Nothing critical is missing.

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% (baseline 3), and the description adds meaning the schema lacks: country defaults to US, page is one-based, and per_page is constrained to 1-100. These specifics go beyond the terse schema descriptions.

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 (List) and resource (Ticketmaster discover cities) plus the scoping dimension (country). It clearly names the downstream sibling ticketmaster-discover-city-events that consumes the returned slug, distinguishing it from venue/event siblings.

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

Usage Guidelines4/5

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

Gives clear context: enumerate discover city destinations for a country and hand the resulting slug to ticketmaster-discover-city-events. It stops short of explicitly stating when NOT to use it (e.g. vs ticketmaster_search_events), so it lacks full alternative routing.

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