Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face dataset rows

hugging_face_datasets_rows_list
Read-onlyIdempotent

Lists rows from a Hugging Face dataset one page at a time; provide the owner and repository name to browse dataset content.

Instructions

List rows from a Hugging Face dataset a page at a time. Requires owner and name. 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": {
      "owner": "<owner>",
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_datasets_rows_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Repository name, without the owner.
pageNoPage number (1-based), `limit` rows a page. Default: 1.
limitNoItems per page, 1-100. A page can hold fewer. Default: 20.
ownerYesRequired. Owner of the repository: a user or organization name.
splitNoSplit name, e.g. `train`. Default: the subset's first split. An unknown name is refused with a 400.
configNoSubset (config) name, e.g. `plain_text`. Default: the dataset's first subset. An unknown name is refused with a 400.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only that results come back a page at a time and that page should be used for pagination; it says nothing about row ordering, maximum retrievable volume, truncation behavior, or auth requirements beyond the required owner/name.

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 purpose and scope, with no wasted clauses. The "Requires `owner` and `name`" sentence is mildly redundant with the schema's required list but does not hurt readability.

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 9-parameter listing tool with no output schema, the description leaves the return shape almost entirely unexplained beyond "Returns a list" — an agent cannot tell whether rows are dicts, arrays, or column-oriented. Pagination intent is covered, but response structure and dataset-version semantics are not.

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 baseline is 3. The description only restates that owner and name are required, adding no meaning about page/limit interaction, split/config resolution, or the odd meta-parameters (context, llm_model, conversation_id) that the schema already documents.

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?

States a specific verb and resource ("List rows from a Hugging Face dataset") plus the paging scope, which is more precise than the title alone. It does not distinguish this from near neighbors such as hugging_face_datasets_get or hugging_face_datasets_viewer_get, so an agent cannot tell from the description alone which one returns row data.

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?

The parenthetical "use page when paginated" gives a light operational hint, and "Requires `owner` and `name`" restates prerequisites. There is no explicit when-to-use versus when-not, and no mention of alternatives like the viewer or search tools for the same dataset.

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