Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face discussions

hugging_face_repos_discussions_list
Read-onlyIdempotent

List discussions and pull requests for a Hugging Face repository by specifying repository type, owner, and name; use pagination to browse results.

Instructions

List the discussions and pull requests of a Hugging Face repository. Requires repoType, 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": {
      "repoType": "<repoType>",
      "owner": "<owner>",
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_repos_discussions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Repository name, without the owner.
pageNoPage number (1-based). Default: 1.
sortNo`recently-created` (default), `trending` or `reactions`.
typeNo`all` (default), `discussion` or `pull_request`.
ownerYesRequired. Owner of the repository: a user or organization name.
queryNoSearch text in titles.
authorNoOnly discussions opened by this account.
statusNo`all` (default), `open` or `closed`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
repoTypeYesRequired. Repository type: `models`, `datasets` or `spaces`.
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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds two useful behavioral facts beyond that: the result is a list, and pagination is handled via the page parameter. It says nothing about result size, ordering defaults, or what happens when no discussions match.

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 action and scope. The middle sentence restating 'Requires repoType, owner and name' duplicates the schema's required list and 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 12-parameter tool with no output schema, the description is thin: it omits that filtering and sorting are possible, which is the main reason an agent would reach for this over the get sibling. The schema compensates for parameter detail, and the pagination note covers return handling, but the overall picture of what the tool can do is incomplete.

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% and every parameter carries a description, including enums and defaults, so the schema does the heavy lifting. The description only restates the three required identity parameters and adds nothing about the filter parameters (type, status, sort, query, author) that meaningfully change results. 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?

States a specific verb and resource: 'List the discussions and pull requests of a Hugging Face repository.' An agent can tell this apart from the sibling 'hugging_face_repos_discussions_get' by the list-vs-get framing, though the sibling is never named explicitly.

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?

Usage is only implied by the resource being listed; there is no statement of when to prefer this over the sibling get tool, nor any mention that the tool supports filtering by type, status, sort, author or query text. The one genuine usage hint is 'use page when paginated', which covers a single case.

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