Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ticketmaster_attraction_reviews

Fetch fan reviews for a Ticketmaster attraction by numeric id, including ratings, review text, venue, date, and an AI summary, with offset and limit controls.

Instructions

List a Ticketmaster attraction's fan reviews. Lists fan reviews for the Ticketmaster attraction with numeric id, with its average_rating, best_rating, total and Ticketmaster's own ai_review_summary. Each review has a rating, title, text, nickname, city, venue and date. offset runs 0 to 9995 (default 0); limit runs 10 to 50 (default 10).

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Ticketmaster attraction id
limitNoReviews per page (10-50)
offsetNoResult offset (0-9995)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It helpfully enumerates the return payload (average_rating, best_rating, total, ai_review_summary plus per-review fields), which substitutes for the missing output schema, but it says nothing about read-only semantics, auth/permission needs, rate limits, or pagination limits (e.g., whether offset 9995 is the ceiling of a total).

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?

Dense and front-loaded, but the opening is redundant: 'List a Ticketmaster attraction's fan reviews' is immediately restated as 'Lists fan reviews for the Ticketmaster attraction with numeric id'. Trimming that duplication would leave a tight, informative definition.

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?

With no annotations and no output schema, the description compensates well by enumerating the returned summary fields and per-review fields plus valid parameter ranges. It is close to complete for a read-only review-list tool; only auth/permission context and total-result behavior are absent.

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% and the schema already documents id, limit (10-50), and offset (0-9995). The description largely repeats those ranges; the only added value is the explicit defaults (0 and 10), so it sits at the baseline for a fully-covered schema.

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 a specific resource (a Ticketmaster attraction's fan reviews), which is inherently distinct from the sibling ticketmaster_attraction (details), ticketmaster_attraction_events, and ticketmaster_attraction_related. An agent can route to it without ambiguity.

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 by the resource ('get reviews for this attraction') but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., use ticketmaster_attraction for details). The ranges given for limit/offset hint at pagination workflow but do not state a condition that selects this tool over siblings.

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