Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face likes

hugging_face_users_likes_list
Read-onlyIdempotent

Retrieve repositories a Hugging Face user liked by supplying their username; use the returned cursor to page through results.

Instructions

List the repositories a Hugging Face user liked. 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_users_likes_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Hugging Face user or organization name, e.g. `clem`.
limitNoItems per page, 1-1000. A page can hold fewer. 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 the safety profile is covered. The description adds only the pagination behavior and the required-parameter reminder, saying nothing about result size, ordering, or what an empty list means.

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, purpose front-loaded, zero filler. 'Requires `name`' and the cursor advice slightly duplicate the schema, which keeps it from a 5, but nothing is wasted.

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 list with 100% schema coverage and no output schema, the description covers purpose, the required input, and the pagination loop. The only real gap is the shape of the returned repository entries, which an agent must discover by calling.

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 the baseline is 3. The description restates that `name` is required and that `cursor` drives pagination — accurate but redundant with the schema, and it adds no new detail such as limits on page size.

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 states a specific verb and resource — 'List the repositories a Hugging Face user liked' — which is clearly distinct from the direction-reversed sibling `hugging_face_repos_likers_list` and from follow/follower lists. It stops short of naming any alternative explicitly, but the purpose is unambiguous.

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 gives the prerequisite ('Requires `name`') and a pagination hint ('use cursor when paginated'), which is implied usage guidance. It never says when to prefer this over the sibling likers/following list tools or what to do when the user is unknown, leaving selection mostly to inference.

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