Retrieve liked tracks from your Deezer account, with an optional count limit. Use this to access favorites for playlist management or music discovery.
Your liked/favorite tracks.
| Name | Required | Description | Default |
|---|---|---|---|
| first | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden for behavioral disclosure. It does not mention that the operation is read-only, whether it lists multiple tracks or returns a single one, pagination behavior, or any authorization needs. The phrase is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short (one phrase), which is concise but lacks necessary content. It is not efficiently front-loaded because there is almost no information to load. The brevity does not earn its place as the content is effectively redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's single parameter, no output schema, and no annotations, the description is critically incomplete. It does not clarify the return value, how the 'first' parameter affects results, or any other contextual detail needed for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one parameter ('first') with no description, and the tool description does not mention it. Schema description coverage is 0%, so the description should compensate but fails to explain the purpose or format of the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Your liked/favorite tracks' is a noun phrase that merely restates the tool name without adding any verb or clarifying the action. It fails to distinguish the tool from siblings like get_favorite_albums or get_favorite_artists, providing no unique context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. The description does not indicate when to use this tool, what prerequisites exist, or how it differs from alternatives such as get_track or get_favorite_artists.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.