Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Hugging Face repository text

hugging_face_search_fulltext
Read-onlyIdempotent

Search Hugging Face READMEs and code files by keyword to locate relevant models, datasets, or spaces, with paginated results for browsing matches.

Instructions

Search the text of Hugging Face READMEs and code files. Requires query. Returns a list (use page 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_search_fulltext"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based), `limit` hits a page. Default: 1. At most 500 hits can be skipped, so deeper pages are not offered.
typeNoOnly this kind of repository.
limitNoItems per page, 1-100. A page can hold fewer. Default: 20.
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

B3.2/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 a return-shape/pagination hint ('use page when paginated'), but omits notable protocol quirks documented only in the schema, such as the 500-hit skip ceiling and the conversation_id echo / no-parallel-calls rule.

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 with the core capability front-loaded and no filler. 'Requires `query`' is slightly redundant with the schema's required list, which is the only wasted clause.

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 7-parameter tool with 3 required parameters and no output schema, the description says only that a list is returned. It is adequate but does not surface the interaction protocol (conversation_id echo, no parallel calls) or the deep-pagination ceiling that materially affect how the tool should be 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?

Schema description coverage is 100%, so every parameter, including context, llm_model and conversation_id, is already fully documented. The description only restates that query is required and gestures at page, 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?

The description names a specific verb and resource: full-text search over HF READMEs and code files. This distinguishes it in kind from metadata-oriented siblings like models_search or datasets_search, but it never names an alternative such as search_global, so an agent must infer the boundary itself.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'Search the text of READMEs and code files' implies a content-search role, but the description never says to prefer it over hugging_face_search_global or the typed *_search tools, leaving routing 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