Skip to main content
Glama

NS Pros MCP Gateway

huggingface__hub_repo_details

Get details for one or more Hugging Face repos (model, dataset, or space): card metadata, license, downloads, files, Space hardware/status, dataset configs, splits, columns and preview rows. Auto-detects type unless specified. For datasets, use operations: overview, dataset_structure, dataset_preview. Use dataset_structure first to discover configs, splits, sizes, and schema. Use dataset_preview only when config and split are known, unless the dataset has a single config/split.

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": {
      "repo_ids": "<repo_ids>"
    },
    "name": "huggingface__hub_repo_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRow count for dataset_preview. Defaults to 5 and is clamped to 1-100.
splitNoDataset Viewer split. Required for dataset_preview when the dataset has multiple config/split options. Discover via dataset_structure.
configNoDataset Viewer config. Required for dataset_preview when the dataset has multiple config/split options. Discover via dataset_structure.
offsetNoRow offset for dataset_preview. Defaults to 0.
repo_idsYesRepo IDs for (models|dataset/space) - usually in author/name format (e.g. openai/gpt-oss-120b)
repo_typeNoSpecify lookup type; otherwise auto-detects
operationsNoDetails to return. Defaults to ["overview"]. For datasets, prefer ["overview", "dataset_structure"] first; then call ["dataset_preview"] with config and split.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that repo type is auto-detected and enumerates the payload per repo type, but says nothing about gated/private repo access, authentication requirements, rate limits, or what happens when a repo ID doesn't exist or a dataset has no viewer support. Read-only behavior is only implied.

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?

Front-loaded with the core purpose and payload in the first sentence, followed by operation sequencing. However, the last two sentences largely duplicate what the 'operations' parameter description already says, so a small amount of text does not earn its place.

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 and seven parameters, the description usefully enumerates the returned fields for each repo type (including Space hardware/status and dataset preview rows), which substitutes well for a missing output schema. It falls short only on access/error semantics for gated or nonexistent repos, which an agent calling this tool may need to handle.

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 limit clamping, offset, config/split discovery, and repo_type auto-detect is already documented in the schema. The description restates the auto-detect behavior and the operations ordering rather than adding format or constraint detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (get details) and resource (Hugging Face repos), then enumerates exactly what details: card metadata, license, downloads, files, Space hardware/status, dataset configs/splits/columns/preview rows. This clearly distinguishes a by-ID details lookup from a sibling search tool without needing to open the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit staged workflow for datasets: 'use dataset_structure first to discover configs, splits, sizes, and schema' and 'use dataset_preview only when config and split are known, unless the dataset has a single config/split.' That is concrete when-to-use guidance. The only gap is that it never contrasts this tool with the sibling search tool for the case where the caller doesn't already have repo IDs.

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.