Crawlora MCP

ticketmaster_attraction_reviews

Read-only

Fetch paginated fan reviews and the aggregate rating and review summary for one Ticketmaster attraction. Use ticketmaster_attraction for attraction details or ticketmaster_attraction_events for its event list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`id`	Yes	Required. Numeric Ticketmaster attraction id.
`limit`	No	Optional. Reviews per page, 10-50. Defaults to 10.
`offset`	No	Optional. Result offset, 0-9995. Defaults to 0.

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 7, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, and an output schema exists to describe returns. The description adds the useful pagination trait and the fact that an aggregate rating/summary is bundled with raw reviews, but discloses nothing about auth, rate limits, or ordering.

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, with the core capability front-loaded and the disambiguation sentence second. Every clause earns its place.

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 read-only, open-world tool with a full output schema and 100%-documented params, the description covers what the agent needs to select and call it correctly. Only minor behavioral details (ordering, freshness of reviews) are absent, which the output schema likely carries.

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% (id, limit 10-50, offset 0-9995 all documented). The word 'paginated' loosely ties to limit/offset but adds no syntax or defaults beyond the schema, so the baseline 3 for schema-carried parameters applies.

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 (fetch) and a precise resource (paginated fan reviews plus aggregate rating and review summary) scoped to one Ticketmaster attraction. An agent can immediately distinguish it from ticketmaster_attraction and ticketmaster_attraction_events without opening any schema.

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?

Explicitly routes to two named alternative siblings for adjacent needs (attraction details, event list), which is strong routing. It leaves the positive case (use this when you need reviews/ratings) implied rather than stated, and names no exclusions, so it falls just short of a 5.

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.