Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face followers

hugging_face_accounts_followers_list
Read-onlyIdempotent

List the followers of a Hugging Face user or organization. Provide the account name, and use the returned cursor to page through results.

Instructions

List the followers of a Hugging Face user or organization. Requires name. 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": {
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_accounts_followers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Hugging Face user or organization name, e.g. `clem`.
limitNoAccounts per page, 10-1000. Default: 100.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep every other parameter the same.
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 safety is covered. The description adds the pagination mechanic and the required-parameter note, but says nothing about what the follower entries contain or how large pages may be beyond what the schema states.

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?

Three short sentences, front-loaded with the verb and resource, with no filler. Minor redundancy in restating that `name` is required, which the schema already marks as required.

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 paginated listing whose parameters are fully documented, the description covers purpose, the required identifier, and paging behavior adequately. The only gap is the absence of return-shape detail, which is minor since there is no output schema.

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 name, limit, cursor, and the analytics parameters are fully documented in the schema itself. The description only echoes that `name` is required and that cursor is for pagination, 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 and resource ('List the followers of a Hugging Face user or organization'), and the direction of the relationship distinguishes it from the sibling hugging_face_users_following_list. It does not name that sibling explicitly, so the differentiation is inferential 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?

Usage is implied by the purpose statement plus the parenthetical 'use cursor when paginated', which gives minimal invocation guidance for paging. There is no explicit when-to-use/when-not guidance and no naming of the alternative tool for the inverse relationship.

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