Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face likers

hugging_face_repos_likers_list
Read-onlyIdempotent

List the accounts that liked a Hugging Face model, dataset, or space repository. Provide repo type, owner, and name to retrieve likers, with cursor pagination for large lists.

Instructions

List the accounts that liked a Hugging Face repository. Requires repoType, owner and 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": {
      "repoType": "<repoType>",
      "owner": "<owner>",
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_repos_likers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Repository name, without the owner.
limitNoItems per page, 1-1000. A page can hold fewer. Default: 100.
ownerYesRequired. Owner of the repository: a user or organization name.
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.
repoTypeYesRequired. Repository type: `models`, `datasets` or `spaces`.
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 and destructiveHint=false, so the safety profile is covered. The description adds only that the result is a list with cursor-based pagination; it says nothing about ordering, result shape, or whether private/hidden likers are omitted — modest added value above 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.

Conciseness4/5

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

Three short sentences, front-loaded with the operation and immediately followed by requirements and return/pagination behavior. No filler, though the requirement sentence duplicates what 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 straightforward read-only list endpoint with fully documented parameters and no output schema, the description covers purpose, inputs and pagination adequately. Only the shape/ordering of returned liker entries is left unstated, which is a minor gap for this complexity level.

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 cursor, limit and repoType is already documented in the schema. The description merely restates which three parameters are required, adding no format or semantic detail beyond that baseline.

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 accounts that liked a Hugging Face repository." An agent can distinguish this from the sibling hugging_face_users_likes_list (likes by a user) without opening a schema, though the description never names that alternative explicitly.

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?

Gives a required-parameter precondition and a pagination hint ("use cursor when paginated"), which implies usage. It does not say when this tool is preferable to nearby siblings such as hugging_face_users_likes_list or hugging_face_accounts_followers_list, so guidance stays 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