Skip to main content
Glama
Sign In
mcp-deezer

mcp-deezer

by Benitoow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_album_from_favorite

Remove an album from your Deezer favorites by providing its album ID. Clears it from your saved albums.

Instructions

Unlike an album.

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": {
      "album_id": "<album_id>"
    },
    "name": "remove_album_from_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.1/5.0
Behavior1/5

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

No annotations are provided, so the description must disclose behavior. However, it is misleading and gives no insight into what occurs when invoked (e.g., data mutation, authorization needs).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (three words), but conciseness should not sacrifice clarity. Here, it is under-specified and fails to communicate essential information, so it does not earn points for efficiency.

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

Completeness1/5

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

Given the simple single-parameter schema and the existence of sibling tools like 'add_album_to_favorite', the description should clearly state its complementary function. It does not, lacking even basic context for operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter 'album_id' has no schema description (0% coverage), and the description adds no meaning. Without specifying what value to provide or expected format, the agent cannot correctly invoke the tool.

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

Purpose1/5

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

The description 'Unlike an album.' is nonsensical and does not convey that the tool removes an album from favorites. It provides no clear verb or resource, making it nearly impossible for an agent to infer its purpose.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives like 'add_album_to_favorite' or 'remove_track_from_favorite'. The description fails to provide any context for appropriate usage.

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