Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face files

hugging_face_repos_files_list
Read-onlyIdempotent

List files and folders in any Hugging Face model, dataset, or space repository to inspect structure, paginate results, and optionally include last commit info.

Instructions

List the files and folders of 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_files_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Repository name, without the owner.
pathNoFolder to list. Default: the repository root.
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`.
revisionNoBranch, tag or commit. Default: the default branch (`main`).
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.
recursiveNo`true` to list every file below the folder.
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.
includeLastCommitNo`true` to add the last commit that touched each file. Pages are then at most 100 entries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description adds that the return is a list and that a cursor drives pagination, which is modest extra context. It says nothing about pagination limits under includeLastCommit, ordering, or what an empty folder yields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three short sentences with no filler. The purpose comes first, then the required inputs, then the return and pagination behavior. Every sentence adds something an agent needs at call time.

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 12-parameter listing tool with no output schema, the description gives enough to call it correctly: the resource, the required inputs, and the list-plus-cursor return shape. It omits that context and llm_model are also required and that includeLastCommit caps pages at 100. Those gaps are already covered in the schema, so they are minor.

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 parameters are already fully documented in the schema. The description only restates which params are required and never explains path, recursive, revision, or includeLastCommit behavior. That baseline of 3 is correct when the schema handles the semantics.

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 gives a specific verb and resource: 'List the files and folders of a Hugging Face repository.' That is clearly distinct from the neighboring readme_get and commits_list siblings. It stops short of naming a nearest alternative or contrasting this tool with a non-recursive or file-metadata tool, so it is clear but not fully differentiated.

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 required identity parameters and gives one usage hint, 'use cursor when paginated.' It does not say when to choose this tool over sibling listing tools, when recursion is appropriate, or any exclusions. Usage is therefore only implied.

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