Skip to main content
Glama
Sign In
mcp-deezer

mcp-deezer

by Benitoow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_track_from_favorite

Remove a track from your Deezer favorite list by providing its track ID. Delete tracks you no longer want to keep your favorites up to date.

Instructions

Unlike a track.

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": {
      "track_id": "<track_id>"
    },
    "name": "remove_track_from_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose behavioral traits such as destructuring, side effects, or permissions. The agent has no understanding of what happens when the tool is invoked.

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

Conciseness1/5

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

The description is extremely short but not concise in a helpful way; it omits essential information and is potentially misleading. Every sentence should earn its place, but here there is only one confusing sentence.

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 simplicity of the tool (one required param, no output schema), the description should clearly state the action and effect. It fails entirely, providing no context for usage.

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 description adds no meaning to the single parameter (track_id). Schema description coverage is 0%, and the description does not explain the parameter's role or format.

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 a track.' is nonsensical and likely a typo; it does not state the verb-resource relationship. The name is clear, but the description fails to convey the tool's 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?

No guidance is provided on when to use this tool versus siblings like remove_album_from_favorite or remove_artist_from_favorite. The agent receives no context for selection.

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