Skip to main content
Glama

NS Pros MCP Gateway

huggingface__hub_repo_search

Search and list Hugging Face models, datasets and Spaces (sort by downloads, likes, trending) with a shared query interface. You can target models, datasets, spaces, or aggregate across multiple repo types in one call. Include links to repositories in your response.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "huggingface__hub_repo_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order (descending): trendingScore, downloads, likes, createdAt, lastModified
limitNoMaximum number of results to return per selected repo type
queryNoSearch term. Leave blank and specify sort + limit to browse trending or recent repositories.
authorNoOrganization or user namespace to filter by (e.g. 'google', 'meta-llama', 'huggingface').
filtersNoOptional hub filter tags. Applied to each selected repo type (e.g. ["text-generation"], ["language:en"], ["mcp-server"]).
repo_typesNoRepository types to search. Defaults to ["model", "dataset"]. space uses keyword search via /api/spaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it does disclose the multi-repo-type aggregation behavior and the available sort axes, which are genuine behavioral traits. It omits result volume/pagination behavior, whether authentication or rate limits apply, and the fact that the per-type limit multiplies results when multiple types are selected.

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?

Three short sentences, front-loaded with the core capability before the targeting nuance. The trailing instruction to include links in the response is slightly off-topic for a tool definition but is short and actionable.

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 six-parameter, zero-required discovery tool with no output schema, the description covers the key complexity (multi-type search and sorting) but leaves the return shape, result-count semantics with limit, and empty-query browsing behavior to the schema. Adequate, not complete.

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 is already documented in structured data, giving a baseline of 3. The description only restates the sort options and the repo-type targeting already covered by the schema, adding no syntax, format, or interaction detail beyond it.

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 ('Search and list Hugging Face models, datasets and Spaces') and adds the facet dimensions (downloads, likes, trending) plus the shared-query-interface notion. It does not explicitly contrast itself with 'huggingface__hub_repo_details', so an agent must infer that details is the per-repo lookup and this is the discovery path.

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?

It states that you can target a single repo type or aggregate across several in one call, which implies the main usage modes. However, there is no explicit when-to-use versus when-to-use-something-else guidance, no mention of when a details lookup is preferable, and no prerequisites or exclusion conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.