Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hugging Face model

hugging_face_models_get
Read-onlyIdempotent

Fetch a Hugging Face model's downloads, tags, card, weights, base models, and evaluation results using owner and name.

Instructions

Get a Hugging Face model with its downloads, tags, card, weights, base models and evaluation results. Requires owner and name.

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>",
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_models_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Repository name, without the owner.
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.
includeNoExtra blocks, comma-separated: `config` (config.json), `spaces` (Spaces that use the model) and `security` (scan result).
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.6/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. The description adds the returned content blocks, which is genuine value, but says nothing about auth requirements, rate limits, or behavior for missing/private repos.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the resource and its returned blocks, then the required inputs. No filler or redundancy.

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?

With no output schema, the description usefully enumerates the returned blocks, which is the main thing an agent needs. The meta-parameters (context, llm_model, conversation_id) are fully explained in the schema, so their absence from the description is acceptable; only the include/revision options go unmentioned.

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 include, revision, context, llm_model and conversation_id is already documented. The description only restates that owner and name are required, adding no meaning beyond the schema; 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 ('Get') and resource ('Hugging Face model') and enumerates what the response contains: downloads, tags, card, weights, base models, evaluation results. That distinguishes it from the search/list siblings, though it never names an alternative explicitly.

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?

The line 'Requires `owner` and `name`' implies this is a detail-fetch for an already-identified model, which is useful context. However, it gives no explicit when-to-use versus hugging_face_models_search or when-not guidance, leaving the agent to infer the routing.

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