Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face trending

hugging_face_trending_list
Read-onlyIdempotent

List trending Hugging Face models, datasets, and Spaces, with optional type and limit filters, to discover what the community is engaging with now.

Instructions

List the models, datasets and Spaces trending on Hugging Face now. Optional inputs: type and limit. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_trending_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo`all` (default), `model`, `dataset` or `space`.
limitNoItems per page, 1-20. A page can hold fewer. Default: 20.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that results reflect current trending state and returns a list, but says nothing about ordering, freshness window, or pagination behavior (the schema's 'items per page' wording implies paging the description never mentions).

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, front-loaded sentences with no filler; the purpose leads. 'Returns a list' is thin but does set a minimal output expectation, so the wording is efficient though not maximally informative.

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 simple read-only listing tool with strong annotations and a fully documented schema, this is adequate. Still, with no output schema the description should say more about what a list item contains or how paging works, and it omits the conversation_id sequencing requirement that affects how the tool is called.

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?

With 100% schema description coverage, the baseline applies. Noting `type` and `limit` as the optional inputs lightly signals which parameters matter for shaping results, but the two required parameters (`context`, `llm_model`) and `conversation_id` — the one with the tricky parallel-call constraint — go unmentioned in the description.

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 set: listing trending models, datasets and Spaces on Hugging Face. 'Trending now' distinguishes it in spirit from the *_search siblings, but it never names an alternative outright, so the differentiation is implied rather than explicit.

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?

There is no when-to-use guidance, no exclusions, and no reference to sibling tools such as hugging_face_models_search or hugging_face_datasets_search. The only hint is that `type` and `limit` are optional, which is schema information restated rather than usage guidance.

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