Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ticketmaster_attraction_events

Retrieve upcoming Ticketmaster events for a specific attraction by numeric ID, with paging and sorting by relevance or date.

Instructions

List an attraction's Ticketmaster events. Lists upcoming Ticketmaster events for the attraction with numeric id. page is zero-based, 0 to 49, default 0; sort is relevance or date (default). Each event has title, start time, time zone, venue, attractions, presales, seat map and status flags such as sold_out and cancelled. The response gives total.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Ticketmaster attraction id
pageNoZero-based page (0-49)
sortNoResult order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "date"
+]
  2. Added

TDQS

A3.8/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 for a read-only list tool: it discloses the pagination ceiling (0-49), the sort options and default (`date`), and the shape of returned events including status flags like `sold_out` and `cancelled`. It does not mention rate limits or auth requirements, keeping it below a 5.

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?

The purpose is front-loaded in the first sentence, and the remaining sentences are information-dense with param defaults and return-field summaries. Slightly repetitive in restating 'list events' twice, but overall efficient.

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?

There is no output schema, so the description appropriately summarizes the returned fields (title, start time, time zone, venue, attractions, presales, seat map, status flags) and the `total` count. This covers what an agent needs to decide whether the result is useful, with only minor gaps like ordering semantics.

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 description coverage is 100%, so the baseline is 3, but the description adds value the schema lacks: default values for `page` (0) and `sort` (date) that the schema omits. The enum options are only restated, not elaborated, so it lands at 4 rather than 5.

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?

The description opens with a specific verb+resource ('List an attraction's Ticketmaster events') and clarifies the required `id` is a numeric attraction id. It is clear and actionable, but does not explicitly distinguish this from closely related siblings such as ticketmaster_search_events or ticketmaster_venue_events, so it stops short of a 5.

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 — supply an attraction id to get its events — but there is no explicit when-to-use guidance, no mention of prerequisites (e.g. that the id must come from an attraction lookup), and no exclusion or alternative named. Minimum-viable routing guidance only.

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