Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer album by barcode

deezer_album_by_upc_get
Read-onlyIdempotent

Fetch Deezer album metadata by UPC or EAN barcode to identify a release and retrieve its title, artist, and related album details.

Instructions

Get a Deezer album from its UPC or EAN barcode, with the same fields as the album lookup. Requires upc.

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

Input Schema

NameRequiredDescriptionDefault
upcYesRequired. UPC or EAN barcode of the album, for example `724384960650`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
languageNoTwo-letter language code for editorial text, such as `fr`. Titles and names are not translated. Default: `en`.
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.7/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 a useful return-shape hint ('same fields as the album lookup') in the absence of an output schema, but says nothing about rate limits, auth, or failure behavior for an unknown barcode.

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 tight sentence with the resource and identifier type front-loaded and no filler. It is appropriately sized, though the trailing 'Requires `upc`' is redundant with the schema and could be dropped.

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 simple read-only lookup with full schema coverage and no output schema, the description supplies the key missing piece (that the response mirrors the album lookup). The sequencing constraint around conversation_id is left entirely to the schema, which is acceptable but slightly incomplete.

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%, including the UPC pattern and example, so the schema carries the parameter burden. The description only repeats the `upc` requirement and adds no meaning about the meta-parameters (context, llm_model, conversation_id) beyond what the schema already documents.

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

Purpose5/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 Deezer album') plus the exact identifier type ('UPC or EAN barcode'), and the clause 'same fields as the album lookup' implicitly distinguishes it from the ID-based deezer_album_get sibling. An agent can tell which lookup to pick from the description alone.

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: the barcode-based identifier signals when this tool applies, and 'Requires `upc`' restates the schema. It never explicitly says to use deezer_album_get when an album ID is available instead, so the alternative routing is left to inference.

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