Skip to main content
Glama
chrischall

setlist-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

setlist_search_artists

Read-only

Search setlist.fm for artists by name or MusicBrainz ID to obtain their MusicBrainz ID (mbid) for retrieving setlists and concert history.

Instructions

Search setlist.fm for artists by name or MusicBrainz ID. Returns matching artists with their MusicBrainz ID (mbid) — use that mbid with setlist_get_artist or setlist_get_artist_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)
sortNoSort order (sortName = default, or relevance)
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.
artistMbidNoArtist's MusicBrainz ID (mbid)
artistNameNoArtist name to search for

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

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds valuable behavioral detail beyond the schema: results include a setlist.fm URL, presentation must cite it as a followable source link (no nofollow), and fallback URL when the result lacks one. This is meaningful operational context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, then provides the essential mbid-linkage and attribution requirements. Each sentence earns its place: the first states the operation, the second connects to sibling tools, and the third gives a citation rule that affects agent behavior. No wasted words.

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 read-only search tool with fully documented parameters, the description covers the main invocation flow: search by name/mbid, receive mbid/url, and use the mbid downstream. It also covers the attribution edge case (missing url). It does not describe result pagination or formatting details, but the schema already documents the page parameter and no output schema exists. This is effectively complete for correct invocation.

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%, with all five parameters described in the input schema itself. The description reinforces that search is by 'name or MusicBrainz ID,' mapping to artistName and artistMbid, but it does not add meaning beyond what the schema already provides. Baseline 3 is appropriate when the schema carries the parameter documentation load.

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 uses a specific verb and resource: 'Search setlist.fm for artists by name or MusicBrainz ID.' It clearly distinguishes itself from sibling tools by stating it returns matching artists with their mbid shape the caller needs for follow-up artist or setlist retrieval. This is a focused, unambiguous purpose.

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 usage context: use this when you need to find artists and then get their mbid for further artist or setlist calls. It names downstream tools but does not explicitly state when to prefer this over alternatives like setlist_search_setlists or setlist_get_artist. The guidance is clear enough for inference but not explicit about exclusion scenarios.

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