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, aliases, tags, and external links (url-rels — Wikidata, Discogs, official site). 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).

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description
`area`	No	Associated area name. Omitted when unknown.
`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.
`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).
`disambiguation`	No	Short qualifier. Omitted when absent.

Schema Changelog

Changes observed during successful MCP inspections.

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

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), so the description is not obliged to restate them. It does add genuine behavioral context beyond the structured fields: the release set is deliberately excluded because it can reach tens of thousands of items. It says nothing about rate limits, caching, or auth, so it is helpful rather than complete.

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?

Two sentences, both front-loaded: the payload fields come first, then the caveat plus the redirect. Nothing is repeated from the title, schema, or annotations, and every clause carries information.

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; the description's field inventory and the explicit exclusion of the release set cover the only non-obvious behavior. For a single-MBID lookup with full annotation and schema coverage, nothing needed to call 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 required MBID parameter and schema description coverage is 100%, including the UUID pattern and whitespace/case tolerance, so the schema already carries the meaning. The description adds nothing about the identifier format, which is the correct baseline for a one-parameter tool whose schema is fully documented.

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?

"Label by MBID" gives a specific verb+resource, and the description enumerates what the label record contains (type, country, life span, label code, area, aliases, tags, url-rels). It also distinguishes itself from siblings by naming the exact alternative for the release set, so an agent can route without reading any other schema.

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 an explicit when-not and an alternative: releases are a potentially huge linked set, so they are not embedded here and should be enumerated with musicbrainz_browse_entities (target_type=release, link.label). That is strong routing guidance, but it does not address the upstream step of obtaining the MBID (e.g. via musicbrainz_search_entities), so it stops short of full when-to-use coverage.

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.