Setlist Fm

Artist

artist

Read-onlyIdempotent

Fetch a setlist.fm artist record by band name or MusicBrainz ID. Pass artist_name ("Radiohead") and the name is resolved to the MBID for you, preferring an exact match so a tribute act does not answer for the band; pass mbid directly when you already have one. Returns artist name, MBID, Ticketmaster ID, sort name, and disambiguation info.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mbid": "79239b12-edad-4280-a524-8344d868a69e"
    },
    "name": "artist"
  }
}

Input Schema

Name	Required	Description	Default
`mbid`	No	MusicBrainz ID, e.g. "a74b1b7f-71a5-4011-9441-d0b5e4122711". Either this or artist_name is required.
`artist_name`	No	Band or performer name, e.g. "Radiohead". Either this or mbid is required.

Output Schema

Name	Required	Description
`url`	No	setlist.fm URL
`mbid`	No	Music Brainz ID
`name`	No	Artist name
`tmid`	No	Ticketmaster ID
`image`	No	Image URL
`sortName`	No	Sort name
`disambiguation`	No	Disambiguation info

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 8, 2026

addedInput schema / properties / artist_name

Added value: +{
+  "description": "Band or performer name, e.g. \"Radiohead\". Either this or mbid is required.",
+  "type": "string"
+}

addedInput schema / properties / mbid / description

Added value: +"MusicBrainz ID, e.g. \"a74b1b7f-71a5-4011-9441-d0b5e4122711\". Either this or artist_name is required."

removedInput schema / required
```
Removed value: -[
-  "mbid"
-]
```

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "mbid": "79239b12-edad-4280-a524-8344d868a69e"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "disambiguation": {
+      "description": "Disambiguation info",
+      "type": "string"
+    },
+    "image": {
+      "description": "Image URL",
+      "type": "string"
+    },
+    "mbid": {
+      "description": "Music Brainz ID",
+      "type": "string"
+    },
+    "name": {
+      "description": "Artist name",
+      "type": "string"
+    },
+    "sortName": {
+      "description": "Sort name",
+      "type": "string"
+    },
+    "tmid": {
+      "description": "Ticketmaster ID",
+      "type": "number"
+    },
+    "url": {
+      "description": "setlist.fm URL",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context about exact-match preference to avoid tribute acts and explains the name-to-MBID resolution process, going beyond the annotations.

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 exceptionally concise: three sentences each serve a distinct purpose (function, parameter usage, return fields). No redundant or filler content.

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

Completeness5/5

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

Given the simple two-parameter tool with 100% schema coverage, output schema, and comprehensive annotations, the description fully covers invocation modes and behavior. It is complete for an agent to select and call this tool.

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 descriptions cover both parameters, but the description enriches them by explaining that artist_name is resolved to an MBID while mbid is used directly, and notes the exact-match preference—details not present 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 tool's purpose with a specific verb ('Fetch') and resource ('setlist.fm artist record'), and it distinguishes itself from siblings like artist_search by emphasizing direct lookup with MBID resolution rather than searching.

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?

Provides clear guidance on when to pass artist_name (to resolve to MBID) versus mbid (when already known), which informs usage. However, it does not explicitly mention alternatives such as artist_search, so exclusions are absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Setlist Fm tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.