Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search all of Hugging Face

hugging_face_search_global
Read-onlyIdempotent

Search Hugging Face models, datasets, Spaces, organizations, users, papers, collections, buckets, kernels, and blog posts by query to find relevant resources.

Instructions

Search Hugging Face models, datasets, Spaces, organizations, users, papers, collections, buckets, kernels and blog posts. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_search_global"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly this kind of result. Omit to search everything.
queryYesRequired. Search text.
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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. Beyond that the description adds only "Returns a list," with no information on result limits, ranking, pagination, or the conversation_id handshake the schema requires before parallel calls.

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 resource scope and the required parameter. No filler or repetition of the title. The only weakness is that the closing "Returns a list" carries little value.

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 five-parameter search tool with no output schema, the description covers what is searched but omits the multi-type narrowing via `type`, result-set behavior, and any sequencing constraint. The analytics-style required parameters are documented in the schema, so the description is adequate but leaves real gaps.

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 the schema already documents every parameter including the enum of searchable types. The description only restates that `query` is required, adding essentially no meaning beyond the input 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?

Names a specific verb (Search) and an explicit enumeration of the resources searched (models, datasets, Spaces, orgs, users, papers, collections, buckets, kernels, blog posts), so an agent knows this is the broad, cross-type search rather than a single-resource lookup. It does not explicitly say it is the umbrella counterpart to the per-type siblings such as hugging_face_models_search, but the enumeration makes the scope clear.

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 gives no when-to-use or when-not-to-use guidance and never mentions the per-type siblings. An agent must infer from the schema alone that the optional `type` parameter narrows results and that type-specific tools presumably exist. Nothing routes the agent between this tool and its many relatives.

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