Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ticketmaster_attraction

Retrieve one Ticketmaster attraction (artist, team, or event entity) by numeric ID, returning profile details and setlists when available.

Instructions

Get a Ticketmaster attraction. Returns one Ticketmaster attraction (artist, team or other event entity) by numeric id: name, synopsis, image, URL, classification (segment, genre, sub-genre) and has_artist_video. Past performance setlists and setlist_source_url appear only when available. An unknown attraction returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Ticketmaster attraction id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned fields, flags conditional data (setlists/setlist_source_url appear only when available), and states error behavior (unknown attraction returns 404). It stops short of disclosing read-only nature or rate/auth constraints, but the key behavioral facts are disclosed.

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?

Front-loaded with the action, followed by tightly packed return-field and edge-case details. Every sentence contributes information an agent can act on, with no filler.

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 simple one-parameter lookup with no output schema, the description compensates by enumerating the return fields and the 404 case. It lacks provenance guidance for the id and read-only confirmation, but is otherwise sufficient to invoke the tool correctly.

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?

Only one parameter exists and schema coverage is 100% ("Numeric Ticketmaster attraction id"). The description repeats the "numeric `id`" semantics, adding nothing beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ("Get a Ticketmaster attraction") and defines what an attraction is (artist, team or other event entity), which disambiguates it from search/event siblings. It does not explicitly name sibling tools like ticketmaster_search_events or ticketmaster_attraction_events, but the single-resource lookup is clear from the text.

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

Usage Guidelines2/5

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

The description implies a prerequisite ("by numeric `id`") but never says when to use this tool versus alternatives such as ticketmaster_suggest, ticketmaster_search_events, or ticketmaster_attraction_events, nor how to obtain a valid id. No when-not guidance is present.

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