Crawlora MCP

ticketmaster_discover_cities

Read-only

List Ticketmaster discover-city destination records for a country, including stable slugs and canonical URLs. Use ticketmaster_discover_city_events with a returned city slug for events or ticketmaster_discover_categories to browse event types.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ticketmaster_discover_cities"
  }
}

Input Schema

Name	Required	Description
`page`	No	Optional. One-based page. Defaults to 1.
`country`	No	Optional. Two-letter country code. Defaults to US.
`per_page`	No	Optional. Cities per page, 1-100. Defaults to 50.

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 chaining-relevant context by noting the records carry stable slugs and canonical URLs, which is what makes the sibling tool callable. It stops short of covering pagination behavior or result volume, but that is a minor gap given the annotations.

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 waste. The resource definition is front-loaded and the routing guidance follows immediately, so the agent gets purpose and next-step in one pass.

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?

Complete for a discovery/list tool: purpose, scope, output-relevant fields for chaining, and explicit alternatives are all present, and a separate output schema means return values need not be restated. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, with page, country and per_page each documented including defaults and the 1-100 range, so the baseline is 3. The description adds no parameter syntax or format detail beyond what the schema already supplies.

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-city destination records) with a clear scope constraint (for a country). It explicitly separates itself from the two sibling tools it could be confused with, so an agent can pick it without opening another schema.

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?

The second sentence gives explicit routing: use ticketmaster_discover_city_events with a returned city slug for events, or ticketmaster_discover_categories to browse event types. This names the alternatives and the condition that selects each, leaving nothing 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?