Skip to main content
Glama
chrischall

setlist-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

setlist_search_venues

Read-only

Find venues on setlist.fm by name, city, state, or country. Get venue IDs and setlist.fm links to retrieve venue details or setlists.

Instructions

Search setlist.fm for venues by name and/or location. Returns matching venues with their venue ID — use it with setlist_get_venue or setlist_get_venue_setlists. Results include a setlist.fm url; when you present this data, cite it as a clickable source link to setlist.fm (their API terms require followable attribution — no nofollow). If a result has no url, link to https://www.setlist.fm instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pNoResult page number (defaults to 1)
nameNoVenue name
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns Setlist.fm's payload untouched. No field projection: this server has no verified record of which Setlist.fm fields matter, and inventing one would risk dropping a field a caller needs.
stateNoState name
cityIdNoCity's geoId
countryNoVenue's country
cityNameNoCity the venue is in
stateCodeNoState code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv0.11.1
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Setlist.fm's payload untouched. No field projection: this server has no verified record of which Setlist.fm fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses an important behavioral requirement: attribution must be followable (no nofollow) per setlist.fm API terms, and provides a fallback URL if none is present. This adds operational context not captured by the annotation. It does not cover rate limits or error behavior, but for a read-only search tool the attribution detail is a notable addition.

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 composed of two sentences: the first defines the core function and usage, the second details attribution requirements. It is front-loaded with the primary purpose and avoids redundancy. The attribution guidance, while specific, is essential for compliance and does not bloat the text unnecessarily. Slightly verbose but well-organized.

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 search tool with no output schema, the description covers the essential aspects: what it searches, what it returns (venue ID and URL), and how to use the results (with get_venue tools). The attribution fallback is also covered. Pagination is implicit via the 'p' parameter in the schema. The description is sufficient for an agent to call this tool correctly without additional clarification.

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 input schema already provides 100% coverage with descriptive comments for all eight parameters, so the baseline is 3. The description only mentions 'name and/or location' which loosely maps to the name, city, state, country fields, but adds no new semantic details beyond what the schema states. It does not clarify relationships between parameters like state vs. stateCode, but that is also documented in the 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?

The description clearly states the action ('Search setlist.fm for venues') with a specific resource and distinguishing scope ('by name and/or location'). It also references related tools (setlist_get_venue, setlist_get_venue_setlists) which differentiates it from sibling search tools like setlist_search_artists or setlist_search_cities. The mention of returning venue IDs makes the tool's purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides clear context by indicating that this search is a precursor to retrieving venue details or setlists ('use it with setlist_get_venue or setlist_get_venue_setlists'). It does not explicitly list exclusions (e.g., when to use search_cities instead), but the phrase 'for venues' inherently communicates its domain. The guidance is adequate for an agent to select this tool appropriately.

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