Skip to main content
Glama
qobuz-mcp
by cheubes

Remove Favorites

remove_favorites
Destructive

Remove albums, artists, or tracks from a user's Qobuz favorites in a single call by supplying their IDs, letting you clean up saved music without deleting items one by one.

Instructions

Remove albums, artists and/or tracks from the user's favorites, in one call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remove_favorites"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_idsNo
track_idsNo
artist_idsNo

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds only the batch notion 'in one call'; it does not say removals are irreversible, that favorites feed the user's library, or that a call with no IDs does nothing.

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?

A single front-loaded sentence with no filler; the batching note 'in one call' is tacked on usefully. It is arguably too short for a destructive multi-parameter tool, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the destructive profile, so return values and safety need not be explained. However, for a destructive tool with three all-optional parameters, the description omits what happens on an empty call, whether removal is idempotent, and any permission or account requirements.

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?

Schema description coverage is reported as 0%, so the description has to carry additional meaning, and it partially does by naming the three entity types (albums, artists, tracks) that map onto album_ids, artist_ids and track_ids. It says nothing about format differences (album IDs are alphanumeric strings, the others are integers), the fact that all three are optional with null defaults, or whether at least one is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (remove) and a specific resource (favorites) plus the entity types affected (albums, artists, tracks). It is distinguishable from add_favorites by the verb, but it never names or contrasts with remove_tracks_from_playlist, which also removes tracks, so the differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. For example, a reader might ask how this differs from removing tracks from a playlist, or whether follow_playlist/unfollow_playlist are better for artist-level changes. The description offers no conditions or alternatives.

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