Skip to main content
Glama
chrischall

musicbrainz-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Submit a user rating to MusicBrainz

musicbrainz_submit_rating
Idempotent

Submit your rating (0–100) for a MusicBrainz entity. Requires OAuth rating scope; use confirm:true to apply, otherwise previews without network call.

Instructions

Set YOUR rating for a MusicBrainz entity (needs OAuth: MUSICBRAINZ_OAUTH_* with the rating scope). Rating is 0–100 (MusicBrainz shows it as 1–5 stars in steps of 20; 0 removes your rating). Without confirm: true it returns a dry-run preview and makes NO network call; with confirm: true it submits. Data from MusicBrainz (https://musicbrainz.org), the open music encyclopedia.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mbidYesMBID of the entity to rate
entityYesEntity type to rate
ratingYesRating 0–100 (0 removes; 20/40/60/80/100 = 1–5 stars)
confirmNoMust be true to proceed. Without this, the tool returns a preview.

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?

Annotations already flag readOnlyHint=false and destructiveHint=false, but the description adds the critical dry-run/confirm behavior and the rating scale (0 removes). This goes beyond the structured hints by explaining the two-phase submission mechanism and the exact effect of rating values, which is essential for safe invocation.

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 three sentences, front-loading the purpose, then auth, then the confirm behavior. No wasted words, and every sentence earns its place by providing actionable information.

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?

Given the tool has no output schema, the description explains the dry-run preview and submission, but does not specify the exact return format or error handling. However, for a submission tool with this scope, the essential behavior is covered, and annotations plus schema handle most edge cases.

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%, but the description adds meaning by explaining the rating scale (0–100 with 20-step stars) and the confirm parameter's dry-run vs submit behavior, which the schema does not fully convey. It reinforces the semantics without duplicating everything.

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 a specific verb ('Set'), resource ('YOUR rating for a MusicBrainz entity'), and clarifies it is a user rating, distinguishing it from other MusicBrainz operations like tags or searches. It also names the required OAuth scope, making the purpose unmistakable.

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 explicit conditions for use: the OAuth requirement and the confirm parameter's role (dry-run preview vs actual submission). It does not explicitly exclude alternatives, but the tool's scope is clear enough that an agent can infer when to use it over siblings like musicbrainz_submit_tags.

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