Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face repositories

hugging_face_accounts_repos_list
Read-onlyIdempotent

List public models, datasets, or Spaces for a Hugging Face user or organization by name, with sorting and cursor pagination for browsing large accounts.

Instructions

List the public models, datasets or Spaces of a Hugging Face account. 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_repos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Hugging Face user or organization name, e.g. `clem`.
sortNoSort order: `downloads`, `likes`, `likes7d`, `likes30d`, `trending`, `created` or `updated`. Default: `updated`.
typeNo`models` (default), `datasets` or `spaces`.
limitNoItems per page, 1-1000. A page can hold fewer. Default: 50.
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 needs no restatement. The description adds two genuinely useful facts beyond that: only public repositories are returned, and results may be paginated via a cursor. It does not mention rate limits, auth requirements, or what happens if the account does not exist.

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 purpose and followed by the pagination mechanics. Little waste, though 'Requires `name`' duplicates the schema's required list and the 100% documented parameter description, making that sentence the weakest of the three.

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 an 8-parameter read-only list tool with full schema coverage and strong annotations, the description covers purpose, visibility scope and pagination. The remaining gap is return-item shape, which matters somewhat since there is no output schema, but the 'Returns a list' statement plus cursor guidance is enough for correct invocation.

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% — every parameter including `sort`, `type`, `limit`, `cursor` and the analytics params is documented in the schema itself. The description only echoes that `name` is required and that the cursor continues a page, adding no syntax or behavioral detail the schema lacks. 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 with scope: 'List the public models, datasets or Spaces of a Hugging Face account.' The 'public' qualifier and the enumerated resource types (mirroring the `type` enum) make the operation unambiguous. It stops short of naming a sibling alternative, so it doesn't reach the sibling-differentiation bar for 5.

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 only implied by the purpose — an agent can infer 'use this to browse an account's repos' — and 'use cursor when paginated' gives one concrete operating hint. There is no explicit when-to-use vs. when-not guidance and no mention of sibling tools like the trending or search variants that overlap in intent.

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