musicbrainz-mcp-server

musicbrainz-mcp-server: get label

musicbrainz_get_label

Read-onlyIdempotent

Label by MBID: type (Original Production, Reissue, Imprint, …), country, life span, label code (the LC number), area and areaId, IPI/ISNI identifiers, aliases, tags, ownership/imprint/distribution relationships, and external links (url-rels — Wikidata, Discogs, official site). Chain areaId into musicbrainz_browse_entities link.area. A label's releases are a potentially huge linked set (a major label can have tens of thousands), so they are NOT embedded here — enumerate them with musicbrainz_browse_entities (target_type=release, link.label).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mbid": "<mbid>"
    },
    "name": "musicbrainz_get_label"
  }
}

Input Schema

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

Output Schema

Name	Required	Description
`area`	No	Associated area name. Omitted when unknown.
`ipis`	No	IPI identifiers as exact strings in upstream order (may be empty).
`mbid`	No	Label MBID.
`name`	No	Label name.
`tags`	No	Community tags/genres (may be empty).
`type`	No	Label type. Omitted when unknown.
`error`	No	Present when the call failed. Absent on success.
`isnis`	No	ISNI identifiers as exact strings in upstream order (may be empty).
`areaId`	No	Area MBID for musicbrainz_browse_entities link.area. Omitted when unknown.
`aliases`	No	Alternate names (may be empty).
`country`	No	ISO country code. Omitted when unknown.
`lifeSpan`	No	Founding/dissolution span. Omitted when unknown.
`sortName`	No	Sortable name form. Omitted when absent.
`labelCode`	No	Label code (LC number), without the "LC" prefix. Omitted when absent.
`externalLinks`	No	External resource links (url-rels) (may be empty).
`relationships`	No	Label ownership, imprint and distribution relationships in upstream order, uncapped (may be empty).
`disambiguation`	No	Short qualifier. Omitted when absent.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 3, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "not": {
-      "required": [
-        "error"
-      ]
-    },
-    "required": [
-      "mbid",
-      "name",
-      "aliases",
-      "tags",
-      "externalLinks"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "mbid",
+      "name",
+      "ipis",
+      "isnis",
+      "aliases",
+      "tags",
+      "externalLinks",
+      "relationships"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / areaId

Added value: +{
+  "description": "Area MBID for musicbrainz_browse_entities link.area. Omitted when unknown.",
+  "type": "string"
+}

addedOutput schema / properties / ipis

Added value: +{
+  "description": "IPI identifiers as exact strings in upstream order (may be empty).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / isnis

Added value: +{
+  "description": "ISNI identifiers as exact strings in upstream order (may be empty).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / relationships

Added value: +{
+  "description": "Label ownership, imprint and distribution relationships in upstream order, uncapped (may be empty).",
+  "items": {
+    "additionalProperties": false,
+    "description": "A typed relationship to another entity (band membership, performer, writer, etc.).",
+    "properties": {
+      "attributes": {
+        "description": "Role modifiers (e.g. \"lead vocals\", \"assistant\", \"co\"). Omitted when none.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "begin": {
+        "description": "Relationship start date. Omitted when absent.",
+        "type": "string"
+      },
+      "direction": {
+        "description": "Relationship direction (\"forward\" | \"backward\"). Omitted when absent.",
+        "type": "string"
+      },
+      "end": {
+        "description": "Relationship end date. Omitted when absent.",
+        "type": "string"
+      },
+      "orderingKey": {
+        "description": "Upstream relationship sequence key, including zero. Omitted when unknown; array order is preserved.",
+        "type": "number"
+      },
+      "targetDisambiguation": {
+        "description": "Qualifier distinguishing the related entity from namesakes. Omitted when absent.",
+        "type": "string"
+      },
+      "targetId": {
+        "description": "MBID of the related entity — chain to the matching get_* tool. Omitted for url targets.",
+        "type": "string"
+      },
+      "targetName": {
+        "description": "Name/title of the related entity. Omitted when absent.",
+        "type": "string"
+      },
+      "targetType": {
+        "description": "Type of the related entity (\"artist\" | \"work\" | \"recording\" | \"label\" | \"url\").",
+        "type": "string"
+      },
+      "type": {
+        "description": "Relationship role (e.g. \"member of band\", \"producer\", \"writer\", \"performance\").",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "targetType"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed3 schema fields changedOct 13, 2026

changedInput schema / properties / mbid / description

Previous value: -"Label MBID (36-character UUID)."New value: +"Label 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 label 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 label 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",
+      "name",
+      "aliases",
+      "tags",
+      "externalLinks"
+    ]
+  },
+  {
+    "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 label 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",
-  "name",
-  "aliases",
-  "tags",
-  "externalLinks"
-]

First observedJun 16, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds real behavioral context beyond them: it discloses the notable exclusion of releases and explains why (a major label can have tens of thousands), preventing an agent from expecting them inline and pointing to the correct alternative. It does not discuss rate limiting or error behaviour on an unknown MBID.

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?

Front-loaded with the field inventory, then the two alternative routing hints are clearly appended. It is dense with parenthetical examples (e.g. 'the LC number', 'Wikidata, Discogs, official site') but each adds disambiguation value, so little is wasted.

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 single-parameter lookup with an output schema and full annotation coverage, the description supplies what the structured fields cannot: field inventory and the critical caveat about releases not being embedded. Nothing needed to invoke it 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?

There is a single parameter with 100% schema description coverage, and the schema already spells out the hyphenated UUID format, whitespace tolerance and required status. The description's 'Label by MBID' adds only the mild clarification that the MBID is a label's rather than another entity's, so the schema does the heavy lifting — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Label by MBID' and then enumerates the exact fields returned (type, country, life span, label code, area, IPI/ISNI, aliases, tags, relationships, url-rels), so an agent knows precisely what entity and detail level this returns. It also implicitly distinguishes itself from the browse sibling by stating what it does not include. Only the explicit verb is missing (it relies on the name/title).

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?

It gives concrete routing instructions: chain areaId into musicbrainz_browse_entities (link.area), and use musicbrainz_browse_entities with target_type=release and link.label to enumerate releases. It does not cover when to prefer this over musicbrainz_search_entities for finding a label in the first place, but the guidance present is specific and actionable.

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.