Skip to main content
Glama

Add to My Discogs Wantlist

discogs_wantlist_add
Idempotent

Add a specific Discogs Release to your Wantlist to track or save it after finding it via search, release, or master-release results. Returns a Release card and leaves your Collection unchanged.

Instructions

Add a Release (one specific pressing) to the Owner's own Discogs Wantlist as a Want.

Use it when the Owner asks to want, save or track a Release found with discogs_search, discogs_get_release or discogs_list_master_releases. Adding a Release that is already on the Wantlist succeeds and changes nothing. Returns a short card of the Release. It never changes the Collection. Discogs' own Wantlist listing can take about 10 seconds to show the new Want. Do not use it to find a Release by name (use discogs_search) or to add a Master: pick one of its Releases first.

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": {
      "release_id": "<release_id>"
    },
    "name": "discogs_wantlist_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
release_idYesDiscogs release_id of the Release to want, e.g. 249504.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description earns credit by making that concrete ('already on the Wantlist succeeds and changes nothing') and by adding facts absent from any structured field: it never touches the Collection, it returns a short card, and Discogs' own listing takes ~10 seconds to reflect the new Want. That eventual-consistency note is exactly the kind of behavior an agent cannot infer elsewhere.

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 action, then usage, then behavior, then exclusions – a clean order with no filler sentences. Minor redundancy: discogs_search is cited both as a source of Releases and again as the alternative for name lookups, which slightly repeats the routing point.

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?

For a one-parameter mutation tool with no output schema, the description covers everything an agent needs: idempotent semantics, the fact that the Collection is untouched, an outline of the return value, a propagation delay, and the Master/Release pitfall. Nothing material is left to inference.

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% and the single parameter is documented, so the baseline is 3; the description adds real meaning by insisting release_id identifies 'one specific pressing' rather than a Master, and by telling the caller to pick a Release from discogs_list_master_releases first. That constrains the value space in a way the schema's 'Discogs release_id' text does not.

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 ('Add a Release ... to the Owner's own Discogs Wantlist as a Want') and immediately disambiguates Release vs Master, which is the key distinction among the sibling tools. An agent can tell this apart from discogs_search and discogs_list_master_releases without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('when the Owner asks to want, save or track a Release found with discogs_search, discogs_get_release or discogs_list_master_releases') and explicit when-not ('Do not use it to find a Release by name (use discogs_search)', 'or to add a Master: pick one of its Releases first'). Alternatives are named with the condition that selects them.

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