Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hugging Face discussion

hugging_face_repos_discussions_get
Read-onlyIdempotent

Retrieve a single Hugging Face repository discussion or pull request, including all comments, to review feedback and conversation context by repo type, owner, name, and number.

Instructions

Get one discussion or pull request of a Hugging Face repository with every comment. Requires repoType, owner, name and number.

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>",
      "number": "<number>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_repos_discussions_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Repository name, without the owner.
ownerYesRequired. Owner of the repository: a user or organization name.
numberYesRequired. Discussion number within the repository, e.g. `1`.
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

A3.6/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 one useful behavioral fact, that all comments are returned, but says nothing about volume/truncation, private-repo auth needs, or ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the resource and the 'every comment' scope front-loaded before the parameter reminder.

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?

For a read-only single-item fetch with a fully documented schema and no output schema, the definition covers the essentials. Minor gaps remain around return shape (comment count, ordering, pagination) that would help an agent size its usage.

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 all seven parameters, including the agent-meta ones (context, llm_model, conversation_id), are documented in the schema. The description only restates four required parameter names without adding format or semantics, so the baseline of 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: retrieve a single discussion or pull request of a Hugging Face repository, scoped to 'with every comment'. This implicitly separates it from the sibling list tool, though it never names that alternative 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?

The phrase 'one discussion ... with every comment' implies you use this to read a single thread's full contents rather than enumerate threads, but there is no explicit when-to-use, when-not-to-use, or named alternative such as the discussions list tool.

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