Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer station

deezer_station_get
Read-onlyIdempotent

Fetch details for a Deezer internet radio station by station ID and return its stream links by bit rate.

Instructions

Get an internet radio station on Deezer with the station's own stream links by bit rate. Requires stationId.

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

Input Schema

NameRequiredDescriptionDefault
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.
stationIdYesRequired. Deezer internet radio station id, for example `15202`.
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, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the useful behavioral detail that stream links are returned grouped by bit rate, but says nothing about error behavior for invalid or geo-restricted station ids, which matters for an open-world lookup.

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 outcome. The trailing 'Requires `stationId`' duplicates what the schema already enforces via required, so it is mild filler rather than added information.

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?

This is a simple read-only getter with full schema coverage, and the description compensates for the absent output schema by saying the response carries the station's stream links by bit rate. What remains missing is minor: where to get a stationId and how invalid ids are handled.

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 every parameter including stationId, context, llm_model and conversation_id is already documented in the schema. The description only restates that stationId is required and adds no format, range, or sourcing guidance beyond the schema's pattern and example.

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?

The description gives a specific verb and resource ('Get an internet radio station on Deezer') and adds what is returned ('the station's own stream links by bit rate'), which separates it from deezer_radios_list and deezer_radio_tracks_list. It stops short of naming any sibling explicitly, so differentiation is inferable rather than stated.

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 single precondition ('Requires `stationId`') implies the single-station lookup use case, but there is no explicit statement of when to prefer this over deezer_radios_list, nor where a station id can be obtained. Usage is implied rather than guided.

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