Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ticketmaster_suggest

Get autocomplete suggestions for Ticketmaster artists, events, teams, or venues from a partial name. Returns matching titles, types, categories, URLs, images, and event counts.

Instructions

Suggest Ticketmaster artists, events, and venues. Returns autocomplete suggestions for a partial artist, event, team or venue name in q. Each suggestion has a title, type, category, URL, image and, when available, an event_count. The response also gives the echoed query and the count of suggestions.

Input Schema

NameRequiredDescriptionDefault
qYesPartial artist, event, team, or venue query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: it returns autocomplete suggestions, includes an event_count only 'when available', and echoes query and count. It does not mention result limits, permissions, or rate behavior, so it stops short of full disclosure.

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?

Three sentences, front-loaded with the purpose, then the input semantics, then the response shape. No filler, though the response-field enumeration could be tightened.

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 usefully enumerates return fields (title, type, category, URL, image, event_count, query, count). It is nearly complete for a one-parameter autocomplete tool, missing only limits on how many suggestions are returned.

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 coverage is 100% and the single parameter is already documented as a partial artist/event/team/venue query. The description restates this without adding format, length, or matching-behavior detail, so the schema does the work.

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 (Suggest) and resources (Ticketmaster artists, events, and venues), plus the key mechanism: autocomplete on a partial name. This distinguishes it in spirit from ticketmaster_search_events, but it never names or contrasts a sibling tool explicitly.

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 phrase 'partial artist, event, team or venue name in q' implies the intended use case (autocomplete/typeahead), but there is no explicit when-to-use or when-not-to-use guidance versus ticketmaster_search_events, ticketmaster_attraction, or other lookups.

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