Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer page embed

deezer_oembed_get
Read-onlyIdempotent

Retrieve embed code and thumbnail for a Deezer track, album, playlist, podcast, or episode URL so you can display or share the content.

Instructions

Get the embed code and thumbnail for a Deezer track, album, playlist, podcast or episode page URL. Requires url.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. A Deezer track, album, playlist, show or episode page URL.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that the response contains an embed code and thumbnail, which is useful return-value context absent an output schema, but says nothing about URL validation failures or embedding restrictions (e.g., private/unavailable pages).

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?

Two short sentences, front-loaded with the action and result type. The trailing 'Requires `url`.' sentence is redundant given required:["url"] in the schema, but the overall size is appropriate.

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 GET with no output schema, the description conveys both what is fetched and what is returned. Full completeness would note eligibility limits (public pages, geo restrictions) and how the missing conversation_id bootstrap applies, but nothing essential to correct invocation is missing.

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 the schema already documents all four parameters including the url format constraint. The description only restates that url is required, adding no meaning beyond the schema; 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+resource: retrieves the embed code and thumbnail for a Deezer page URL, and enumerates the supported entity types (track, album, playlist, podcast, episode). It is clearly distinguishable from metadata siblings like deezer_track_get, though it does not explicitly contrast itself with the similarly named deezer_pages_get.

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?

The supported URL types imply when the tool applies, but there is no explicit guidance on when to prefer it over deezer_track_get/deezer_album_get for embedding vs. metadata, nor any stated prerequisites or exclusions.

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