Skip to main content
Glama
Sign In
setlist-mcp

setlist-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

setlist_search_setlists

Read-onlyIdempotent

Find concert setlists on setlist.fm by artist, venue, city, date, or tour. Filter results to pinpoint specific shows or list all performers at a venue, excluding empty setlists.

Instructions

Search setlist.fm for concert setlists. Filter by any combination of artist, venue, city, country, tour, date, or year (provide at least one). Combine filters to disambiguate — artistName + date can span multiple cities, so add cityName/cityId or venueName/venueId to pin the exact show. Omit the artist and pass venueName/venueId + date to list EVERY performer at a venue or festival that day. Every result includes songCount, setCount, and hasSongs, so you can skip empty 'stub' setlists (hasSongs: false) without a second fetch. 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

NameRequiredDescriptionDefault
pNoResult page number (defaults to 1)
dateNoEvent date, ISO yyyy-MM-dd (e.g. 2025-08-28)
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.
yearNoEvent year
stateNoState name
cityIdNoCity's geoId
venueIdNoVenue ID
cityNameNoCity name
tourNameNoTour name
stateCodeNoState code
venueNameNoVenue name
artistMbidNoArtist's MusicBrainz ID (mbid)
artistNameNoArtist name
countryCodeNoCountry code (ISO 3166-1 alpha-2)
lastUpdatedNoOnly setlists updated on/after this UTC time, ISO yyyy-MM-dd or yyyy-MM-ddTHH:mm:ss

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.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world behavior, so the description usefully layers on non-structural traits: the minimum-one-filter constraint, the presence of songCount/setCount/hasSongs for skipping stub setlists without a second fetch, and the setlist.fm attribution/link requirement. It does not disclose pagination volume or result caps tied to the `p` parameter, which is the remaining gap.

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?

Purpose is front-loaded in the first sentence, followed by filtering guidance, the disambiguation rule, and the attribution rule — a logical order. It is dense but every sentence carries information; slight repetition around filter combinations keeps it from a top mark.

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 15-parameter search with no output schema, the description covers the required-input constraint, result fields (songCount, setCount, hasSongs), stub-setlist handling, and downstream citation obligations. Pagination limits and expected result volume remain unaddressed, but nothing needed to select or call the tool correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real semantic value beyond field definitions — how artistName/date can span multiple cities and how cityName/cityId or venueName/venueId pin the exact show, plus the artist-omitted venue+date pattern. It stops short of explaining `view` or the geo-id vs name parameters, which the schema already covers.

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?

States a specific verb and resource ("Search setlist.fm for concert setlists") and immediately scopes it by the filterable dimensions, which separates it from siblings like setlist_get_setlist or setlist_get_artist_setlists. An agent can identify the tool's role without opening the schema.

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

Usage Guidelines5/5

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

Explicitly states the when-to-use conditions: at least one filter required, combine filters to disambiguate, and the non-obvious pattern of omitting artistName with venueName+date to enumerate every performer at a venue/festival. That last case is exactly the guidance an agent would otherwise have to guess at.

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