Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer account connections

deezer_user_connections_list
Read-onlyIdempotent

List a Deezer account's followers or following accounts by specifying userId and kind; use cursor-based pagination to retrieve additional pages.

Instructions

List the accounts that follow a Deezer account, or that it follows. Requires userId and kind. Returns a list (use cursor when paginated).

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>",
      "kind": "<kind>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_user_connections_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesRequired. Which side of the follow relationship to list.
limitNoItems per page, 1 to 1000. Default: 100.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other parameters the same.
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.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 largely covered. The description adds the useful behavioral detail that results are paginated and driven by a cursor, but says nothing about visibility/privacy of follow lists, ordering, or empty-result behavior.

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 with the capability first and the prerequisites/pagination after; nothing is buried. The 'Requires `userId` and `kind`' clause lightly duplicates the schema, keeping it just short of a 5.

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, non-destructive list endpoint with no output schema and fully described parameters, the description covers what the tool returns (a list of accounts) and how to page through it. The remaining gaps (result ordering, privacy semantics) are minor for this tool's 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%, so every parameter including kind, cursor, context and llm_model is already documented. The description restates that userId and kind are required and that cursor drives paging, adding only mild reinforcement rather than new 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?

The description uses a specific verb and resource ('List the accounts that follow a Deezer account, or that it follows') and the 'kind' enum pins down which direction of the relationship is returned. It distinguishes followers vs following clearly, though it does not explicitly contrast itself with siblings such as deezer_user_get or deezer_user_library_list.

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?

It states the prerequisites ('Requires `userId` and `kind`') and gives a practical pagination instruction ('use cursor when paginated'), which implies usage. However, it never says when to prefer this over related user tools or what to do when a user has no connections, so guidance remains implicit.

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