Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ticketmaster_search_events

Search Ticketmaster events by artist, event, team, or venue. Sort results by relevance or date and page through matching listings.

Instructions

Search Ticketmaster events. Searches Ticketmaster events by artist, event, team, or venue. A zero total with an empty events list is a valid no-results response. The sort enum accepts relevance and date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesArtist, event, team, or venue query
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

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries full responsibility for behavior disclosure. It does disclose that an empty events list with zero total is a valid no-results response, which is useful. However, it omits other behavioral aspects like pagination limits, rate limiting, or side effects (likely none). The single behavioral note helps but leaves gaps.

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 description is concise at three sentences and front-loads the primary purpose. The inclusion of the sort enum is slightly redundant with the schema, but the no-results note adds value. Overall, it is efficient without excessive padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple search tool with three parameters and no output schema. The description adequately covers the query types and hints at the response shape (total and events list) via the no-results note. However, it does not explicitly describe the return format or any other edge cases, leaving some room for improvement given the absence of an output schema.

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?

The schema descriptions cover all three parameters (100% coverage), so the baseline is 3. The description's mention of the sort enum accepting 'relevance' and 'date' is redundant with the schema. It adds no new semantic meaning beyond what is already structured, so it stays at baseline.

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 clearly states the verb and resource ('Search Ticketmaster events') and enumerates the search targets (artist, event, team, venue). This gives a specific actionable purpose. However, it does not explicitly differentiate from sibling tools like ticketmaster_venue_events or ticketmaster_attraction_events, which are more specialized but overlap in intent.

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?

The description implies when to use it (searching by artist, event, team, venue) but provides no explicit guidance on when to prefer it over alternatives such as seatgeek_search or ticketmaster_venue_events. It does offer a tip about valid no-results responses, but no clear when/when-not framework.

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