Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer track lyrics

deezer_track_lyrics_get
Read-onlyIdempotent

Retrieves a Deezer track's lyrics with line and word timings, writers, copyright and licence details. Use it to display synced lyrics or confirm when no lyrics are available for a track ID.

Instructions

Get a track's lyrics with line and word timings, writers, copyright and licence, or none when Deezer shows no lyrics. Requires trackId.

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": {
      "trackId": "<trackId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_track_lyrics_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
trackIdYesRequired. Deezer track id, for example `3135556`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing the response contents (timings, writers, copyright, licence) and the 'no lyrics' outcome. It stops short of describing response shape or sync granularity, so it is good but not rich.

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 tightly written sentence that front-loads the verb, resource and returned fields, with the edge case appended. Nothing is wasted, though the closing 'Requires trackId' is near-redundant with the schema's required list.

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

Completeness4/5

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

For a read-only tool with no output schema, the description carries the return-value explanation well by naming the fields and the empty case. It omits the format of the timing data and any note on licensing restrictions, which would make it fully complete.

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 100%, so all four parameters — including trackId's pattern and example, plus context, llm_model and conversation_id — are fully documented in the schema. The description's 'Requires trackId' only restates the required field and adds no new syntax or constraint meaning, so the baseline 3 applies.

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 and resource ('Get a track's lyrics') and enumerates the payload (line and word timings, writers, copyright, licence). It also names the empty-result case ('or none when Deezer shows no lyrics'), which helps an agent distinguish it from plain metadata tools like deezer_track_get, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: it is clearly the lyrics lookup for a given trackId and nothing else. There is no statement of when to prefer it, no exclusions, and no mention of what to do if lyrics are missing (e.g., whether to fall back to another source).

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