Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Hugging Face Spaces

hugging_face_spaces_search
Read-onlyIdempotent

Search Hugging Face Spaces by keyword, author, SDK, or tags and sort results to find suitable demos and apps. Paginate with a cursor to browse more matches.

Instructions

Search Hugging Face Spaces by keyword, SDK and tags. Optional inputs: query, author, sdk, tags, sort and 3 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_spaces_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sdkNoOnly Spaces built with this SDK.
sortNoSort order: `downloads` (last 30 days), `likes`, `likes7d`, `likes30d`, `trending`, `created` or `updated`. Default: `trending`.
tagsNoComma-separated tags the repository must all have, e.g. `text-classification,pytorch` or `license:mit`.
limitNoItems per page, 1-1000. A page can hold fewer. Default: 50.
orderNo`desc` (default) or `asc`. `asc` only works with `sort=created`.
queryNoSearch text. Matches repository ids, tags and card text.
authorNoOnly repositories owned by this user or organization.
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

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral fact that annotations do not: it returns a list and pagination is handled via cursor. It says nothing about result ordering defaults or result size, though the schema covers those.

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 core action and ending with the return/pagination fact where it belongs. The 'and 3 more' clause is wasted text that could have been omitted or spelled out, which keeps it from a 5.

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 an 11-parameter tool with no output schema, the definition is thin: it never mentions the required context/llm_model/conversation_id plumbing (the schema carries that, including the no-parallel-calls constraint) nor how filters interact. It is callable from the schema alone but leaves the agent without routing guidance against the semantic-search sibling.

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?

With schema description coverage at 100%, the schema already documents every parameter including enums for sdk, sort and order and the cursor contract. The description mostly restates parameter names and then truncates with 'and 3 more', which adds no meaning and is less informative than the schema itself, so baseline 3 is appropriate.

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 opens with a specific verb and resource ('Search Hugging Face Spaces') and names the facets it matches on (keyword, SDK, tags), which is enough for an agent to know what it hits. It does not distinguish itself from the sibling hugging_face_spaces_semantic_search or from the models/datasets/kernels search tools, so an agent must infer that this is the lexical/keyword search.

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 statement of when to prefer this over semantic search or over the entity-specific search siblings; the 'keyword' wording only weakly implies the contrast. No prerequisites, no exclusions, and no guidance on combining the filter parameters (e.g. query plus author plus tags).

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