musicbrainz-mcp-server

musicbrainz-mcp-server: get release

musicbrainz_get_release

Read-onlyIdempotent

One edition's full detail by MBID: the tracklist (media → tracks → recordings with lengths and recording MBIDs), label + catalog number, barcode, country, release date, format, packaging, text representation (language/script), and a cover-art availability stub. Track lengths are rendered m:ss (stored as milliseconds upstream). For the actual cover image URLs, call musicbrainz_get_cover_art with this release MBID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mbid`	Yes	Release MBID (hyphenated hexadecimal UUID; surrounding whitespace and uppercase accepted).

Output Schema

TableJSON Schema

Name	Required	Description
`date`	No	Release date. Omitted when absent.
`mbid`	No	Release MBID.
`error`	No	Present when the call failed. Absent on success.
`media`	No	Media (discs) with their tracklists (may be empty).
`title`	No	Release title.
`script`	No	Text-representation script code. Omitted when absent.
`status`	No	Release status (Official, Promotion, Bootleg, …). Omitted when absent.
`barcode`	No	Barcode (UPC/EAN). Omitted when absent; empty string upstream means "known to have none".
`country`	No	Release country code. Omitted when absent.
`coverArt`	No	Whether cover art exists (availability stub from WS/2).
`language`	No	Text-representation language code. Omitted when absent.
`labelInfo`	No	Label / catalog-number pairings (may be empty).
`packaging`	No	Packaging type (Jewel Case, Digipak, …). Omitted when absent.
`artistCredit`	No	Credited artists (may be empty).
`disambiguation`	No	Short qualifier. Omitted when absent.
`releaseGroupId`	No	Parent release-group MBID — chain to musicbrainz_get_release_group. Omitted when absent.
`artistCreditString`	No	Display string of the artist credit with join phrases.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 13, 2026

changedInput schema / properties / mbid / description

Previous value: -"Release MBID (36-character UUID)."New value: +"Release MBID (hyphenated hexadecimal UUID; surrounding whitespace and uppercase accepted)."

addedInput schema / properties / mbid / pattern

Added value: +"^\\s*[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{12}\\s*$"

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_mbid`: The MBID is malformed or the all-zeros sentinel (MusicBrainz returns HTTP 400). `entity_not_found`: The MBID is well-formed but no release exists with it (MusicBrainz returns HTTP 404). Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_mbid`: The MBID is malformed or the all-zeros sentinel (rejected before fetch), or MusicBrainz rejects it with HTTP 400. `entity_not_found`: The MBID is well-formed but no release exists with it (MusicBrainz returns HTTP 404). Other values are possible when a failure originates below the handler."

Changed6 schema fields changedAug 21, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "mbid",
+      "title",
+      "artistCredit",
+      "artistCreditString",
+      "labelInfo",
+      "media",
+      "coverArt"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_mbid`: The MBID is malformed or the all-zeros sentinel (MusicBrainz returns HTTP 400). `entity_not_found`: The MBID is well-formed but no release exists with it (MusicBrainz returns HTTP 404). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_mbid",
+            "entity_not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "mbid",
-  "title",
-  "artistCredit",
-  "artistCreditString",
-  "labelInfo",
-  "media",
-  "coverArt"
-]

First observedJun 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover safety (readOnly, idempotent, openWorld), so the bar is lower. The description adds real behavioral context: track lengths are rendered m:ss though stored as milliseconds upstream, and it returns a cover-art availability stub rather than images. It does not mention pagination or error behavior, but for a read-only lookup this is solid.

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?

Two dense sentences, front-loaded with what the tool returns, and the sibling call-out lands last where it belongs. It is on the long side for a single-parameter lookup, but each clause maps to a distinct returned field rather than padding.

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?

An output schema exists, so return values need no explanation, yet the description still summarizes the payload shape and flags the m:ss rendering quirk and the cover-art stub. Nothing needed to call this correctly is missing.

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 description coverage is 100% and the single mbid parameter is fully documented in-schema including the UUID pattern and whitespace tolerance. The description adds only 'by MBID', so the baseline 3 applies.

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 ('get release' / 'One edition's full detail by MBID') and enumerates what the detail contains (tracklist, label, barcode, country, date, format, packaging). The agent can immediately distinguish it from get_release_group, get_recording, and get_cover_art.

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?

Explicitly routes the agent to a sibling: 'For the actual cover image URLs, call musicbrainz_get_cover_art with this release MBID.' This is a clear when-to-use-next rule. It lacks guidance on release vs release_group selection, so it stops short of a 5.

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

All musicbrainz-mcp-server 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.