Skip to main content
Glama

Remove from My Discogs Wantlist

discogs_wantlist_remove
Destructive

Removes a specific release from the owner's Discogs Wantlist using its release_id. Use only after confirming the release, since the date added is permanently lost.

Instructions

Remove a Want from the Owner's own Discogs Wantlist, by the release_id of its Release.

Use it only when the Owner asks to remove, drop or delete a Want, and confirm the Release with them first: the Want's date added is lost. Find the release_id with discogs_list_wantlist. A Release that is not on the Wantlist is an error. It never changes the Collection. Discogs' own Wantlist listing can take about 10 seconds to show the change. Do not use it to tidy up the Wantlist on your own, or because a Want is now in the Collection, unless the Owner asks.

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_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
release_idYesDiscogs release_id of the Want to remove, 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 flag destructiveHint=true and openWorldHint=true, but the description adds consequences the annotations cannot convey: the date added is permanently lost, a release not on the Wantlist is an error, the Collection is untouched, and Discogs' own listing may lag ~10 seconds. These are concrete, hard-to-discover operational traits that directly affect how an agent sequences calls and reports results.

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 and scope, then layered with preconditions and exclusions; every sentence carries operational weight. It is slightly long and the closing prohibition restates the 'only when the Owner asks' condition, but that redundancy is defensible for a destructive tool.

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 single-parameter destructive tool with no output schema, the description covers the mutation target, irreversibility, error condition, side-effect boundary, downstream propagation delay, and agent-initiated-use prohibition. Nothing an agent needs to call this safely is missing.

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 schema already documents release_id with an example and exclusiveMinimum, so the baseline is 3. The description adds real value by naming the acquisition path (use discogs_list_wantlist to find the id) and by tying the parameter to the precondition of confirming the release, though it adds no format or validation detail beyond the schema.

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 — 'Remove a Want from the Owner's own Discogs Wantlist, by the release_id of its Release' — and immediately bounds scope with 'It never changes the Collection', which separates it from collection-mutating siblings. An agent can identify exactly what is affected and what is not without opening the 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?

Gives explicit when-to-use ('only when the Owner asks to remove, drop or delete a Want'), a precondition ('confirm the Release with them first'), a discovery alternative ('Find the release_id with discogs_list_wantlist'), and explicit when-not-to ('Do not use it to tidy up the Wantlist on your own, or because a Want is now in the Collection'). This is the full when/when-not/alternative triad.

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