Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Hugging Face collections

hugging_face_collections_search
Read-onlyIdempotent

Search Hugging Face collections by query or owner, and find collections containing a specific model, dataset, Space, or paper.

Instructions

Search Hugging Face collections, or find the collections that contain a model, dataset, Space or paper. Optional inputs: query, owner, item, sort, limit and 1 more. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_collections_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNoOnly collections that contain this item, e.g. `models/openai-community/gpt2` or `papers/1706.03762`.
sortNo`trending` (default), `upvotes` or `lastModified`.
limitNoItems per page, 1-100. A page can hold fewer. Default: 10.
ownerNoOnly collections this account curates.
queryNoSearch text in titles and descriptions.
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?

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no restating. The description adds two genuinely useful behavioral facts beyond that: the result is a list, and pagination is driven by a cursor. It stops short of describing ranking, result shape, or any rate/scope limits.

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 primary capability and the alternate mode, with no filler. The phrase 'and 1 more' is a small blemish — it gestures vaguely at `cursor` instead of either naming it or omitting the enumeration entirely.

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 read-only, open-world search with full schema coverage and no output schema, an agent has everything it needs to call this correctly, and the cursor note covers the main non-obvious workflow (repeat the call with identical other parameters). The remaining gap is routing between this tool and neighboring search tools, which the description does not address.

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 every parameter including the required `context`/`llm_model` analytics params and the cursor contract is already documented in the schema. The description adds nothing beyond a bare enumeration ('query, owner, item, sort, limit and 1 more'), which is why 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 and resource ('Search Hugging Face collections') and adds a second, clearly stated mode ('find the collections that contain a model, dataset, Space or paper'). This distinguishes it from the sibling hugging_face_collections_get, but it never names any other collection-related alternative, so the differentiation is inferred rather than stated.

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 implied through the two modes: free-text/owner search versus item containment lookup, and the `item` example clarifies what form that filter takes. However there is no explicit when-to-use/when-not-to-use guidance and no mention of when to prefer hugging_face_collections_get or a global search sibling instead.

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