Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get public Deezer account

deezer_user_get
Read-onlyIdempotent

Retrieve a Deezer account's public profile—display name, country, and profile picture—by providing its numeric userId.

Instructions

Get the public profile of a Deezer account: display name, country and picture. Requires userId.

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

Input Schema

NameRequiredDescriptionDefault
userIdYesRequired. Deezer account id, for example `753546365`.
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description adds only that the data is the 'public profile' and what fields come back; it says nothing about auth requirements, rate limits, or behavior on a nonexistent/private account, so it adds modest value beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the verb and resource, then the returned fields, with zero filler. Every clause contributes either identification or return-value 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 single-id read tool with full annotation coverage and a 100%-documented schema, and with no output schema the description usefully enumerates the returned fields. What remains missing — error behavior for invalid or private accounts — is minor for a tool of this complexity.

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 `userId` pattern and an example, so the schema carries the parameter burden and the baseline of 3 applies. The description's 'Requires `userId`' merely restates the schema's required flag and adds no format or edge-case meaning.

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 the public profile of a Deezer account') and enumerates the returned fields (display name, country, picture), which distinguishes it from the sibling list tools such as deezer_user_library_list and deezer_user_playlists_list. It stops short of naming an alternative explicitly, but an agent can tell what this tool returns without opening the schema.

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 implied rather than stated: the tool is a lookup keyed on `userId`, and 'Requires `userId`' signals the precondition. There is no explicit when-to-use/when-not guidance and no pointer to a sibling such as deezer_user_connections_list for related data, so the agent must infer routing from the name and description alone.

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