Skip to main content
Glama
chrischall

musicbrainz-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Add or remove entities in a MusicBrainz collection

musicbrainz_modify_collection
Idempotent

Manage your MusicBrainz collections by adding or removing entities like releases and artists. Preview changes without network calls, then confirm to apply.

Instructions

Add or remove entities (releases, artists, recordings, release-groups, works, labels, places, areas, events) in one of YOUR MusicBrainz collections (needs OAuth: MUSICBRAINZ_OAUTH_* with the collection scope). Get the collection MBID from its URL (musicbrainz.org/collection/). Without confirm: true it returns a dry-run preview and makes NO network call; with confirm: true it applies the change. Data from MusicBrainz (https://musicbrainz.org), the open music encyclopedia.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mbidsYesMBIDs of the entities to add/remove
actionYesWhether to add to or remove from the collection
confirmNoMust be true to proceed. Without this, the tool returns a preview.
collectionYesMBID of the target collection
entityTypeYesPlural entity type the collection holds (e.g. "releases")

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. First observedv0.2.2

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses critical behaviors: it requires OAuth, and without confirm:true it returns a dry-run preview and makes NO network call. This significantly informs the agent about side effects and safety, exceeding what annotations convey.

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 compact and front-loaded with the action and entity types, then quickly covers OAuth, MBID sourcing, and the dry-run/confirm mechanism. Every sentence earns its place with no redundancy.

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?

The description covers the essential operational details for a modification tool: authentication, dry-run behavior, and how to identify the collection. It does not mention the response format or error handling, but given the absence of an output schema and the straightforward nature of the operation, it is sufficiently complete for an agent to invoke correctly.

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 coverage is 100% with descriptions for every parameter, but the tool description adds valuable semantics: it explains that confirm gates the actual change, tells how to get the collection MBID from a URL, and notes entityType is plural. This enriches the schema baseline.

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 states the precise action (add or remove) and the resource (entities in a MusicBrainz collection), and enumerates the supported entity types. It clearly distinguishes this modification tool from siblings like search, browse, and lookup, which have different purposes.

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?

The description gives clear context: it operates on the user's own collections, requires OAuth with collection scope, and explains how to obtain the collection MBID from its URL. It does not explicitly mention alternatives or when not to use it, but the purpose is unambiguous and the sibling tools are clearly different actions.

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