Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hugging Face collection

hugging_face_collections_get
Read-onlyIdempotent

Retrieve a Hugging Face collection by owner and slug, returning every item and the curator's notes for complete collection review.

Instructions

Get a Hugging Face collection with every item and the curator's notes. Requires owner and slug.

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": {
      "owner": "<owner>",
      "slug": "<slug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_collections_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Collection slug without the owner, e.g. `gemma-4-69ce8ad93186d46744cb42f1`.
ownerYesRequired. Owner of the collection: a user or organization name.
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, openWorld and non-destructive, so the safety profile is covered. The description contributes one genuinely useful behavioral fact — the response contains all items and curator notes — but says nothing about size limits, truncation, or pagination for large collections. That is a modest add over the annotations, consistent with a 3.

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 short sentences, front-loaded with the action and payload scope. The second sentence largely repeats the schema's `required` array, so it earns less than full marks, but there is no filler.

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 getter with full schema coverage, complete annotations, and no output schema, the description supplies what an agent needs: what is fetched, what comes back, and what identifiers are required. Only the absence of any sibling routing or large-collection behavior keeps it below 5.

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 patterns and per-parameter explanations, so the schema does the heavy lifting. The description restates only that `owner` and `slug` are required, adding no format or scoping detail beyond the schema (e.g., that slug excludes the owner prefix). 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?

States a specific verb and resource ('Get a Hugging Face collection') and adds scope detail: the response includes every item plus the curator's notes. That distinguishes it in substance from a collections search, though it never names the sibling. Clear enough for an agent to pick it without opening the schema.

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?

The description says only that `owner` and `slug` are required, which is a prerequisite rather than when-to-use guidance. It never contrasts with hugging_face_collections_search or says when a single-collection fetch is the right call versus listing/searching. Usage is left entirely to inference.

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