Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face commits

hugging_face_repos_commits_list
Read-onlyIdempotent

Lists the commit history of a Hugging Face model, dataset, or space repository, using owner, repository name, and optional pagination to browse changes.

Instructions

List the commit history of a Hugging Face repository. Requires repoType, owner and name. Returns a list (use page 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_commits_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Repository name, without the owner.
pageNoPage number (1-based). Default: 1.
limitNoItems per page, 1-50. A page can hold fewer. Default: 50.
ownerYesRequired. Owner of the repository: a user or organization name.
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.
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 structurally. The description adds a modest amount beyond that by indicating the return shape ('returns a list') and pointing at the page parameter for pagination. It does not describe ordering, cursor semantics, or behavior at the end of history, so the added context is limited.

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 purpose, with no filler. The middle sentence restates required fields the schema already enforces, which is mild redundancy but serves as a quick-read preface.

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 nine-parameter list operation with full schema documentation and comprehensive annotations, the description plus structured data cover what an agent needs: resource identity, required identifiers, and paging. The absence of an output schema is partly mitigated by 'returns a list', though it could say more about item contents or sort order.

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% across all nine parameters, so the schema already explains name, owner, repoType, revision, page, limit, and the context/llm_model/conversation_id plumbing. The description only echoes the three required parameters and gestures at page usage, adding no format or semantics beyond the schema. Baseline 3 is appropriate when the schema carries the load.

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+resource: 'List the commit history of a Hugging Face repository'. That is clearly distinguishable from sibling readers like repos_files_list, repos_readme_get, or repos_discussions_list, which target different resources. It stops short of naming an alternative explicitly, so it lands at 4 rather than 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?

It states the mandatory identifiers (repoType, owner, name) and adds a pagination cue ('use page when paginated'), which is enough to call the tool correctly. It never says when to prefer this over a sibling or what conditions would make commit listing the wrong choice, so guidance is implied rather than explicit.

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