Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face recent changes

hugging_face_changes_list
Read-onlyIdempotent

List recently changed Hugging Face models, datasets, Spaces, papers, or blog posts by type to track updates and discover new work.

Instructions

List the Hugging Face models, datasets, Spaces, papers or blog posts that changed most recently. Requires type. Returns a list.

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": {
      "type": "<type>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_changes_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesRequired. What to list: `models`, `datasets`, `spaces`, `papers` or `blog`.
limitNoItems per page, 1-1000. A page can hold fewer. Default: 100.
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

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only 'Returns a list', which restates the tool name rather than revealing anything new — it says nothing about ordering guarantees, the recency window, or pagination behavior.

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?

Two tight sentences with the resource scope front-loaded and no preamble. 'Returns a list.' is close to filler for a tool whose name already ends in _list, but the overall size is appropriate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with rich annotations and a fully described schema, the essentials are present. However, the description never clarifies the recency window ('most recently' is undefined) or how paging works, and the schema exposes only `limit` with no cursor parameter, leaving continuation behavior unaddressed anywhere.

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%, including a documented enum for `type`, the 1-1000 limit range with a default of 100, and detailed guidance for `context`, `llm_model` and `conversation_id`. The description's 'Requires `type`' merely repeats the schema, so the 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?

The description gives a specific verb plus resource family and enumerates the five listable entity types (models, datasets, Spaces, papers, blog posts), so an agent can tell it apart from narrower siblings like hugging_face_blog_posts_list or hugging_face_papers_daily_list. It does not explicitly name those alternatives, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Beyond 'Requires `type`' and the recency framing, there is no when-to-use or when-not-to-use guidance. Nothing tells the agent why it would pick this over hugging_face_trending_list, hugging_face_blog_posts_list, or hugging_face_papers_daily_list, even though those siblings overlap in output.

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