Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hugging Face paper

hugging_face_papers_get
Read-onlyIdempotent

Fetch a Hugging Face paper's authors, abstract, and upvotes by arXiv ID to review or cite research directly in your workflow.

Instructions

Get a Hugging Face paper with its authors, abstract and upvotes. Requires arxivId.

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": {
      "arxivId": "<arxivId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_papers_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
arxivIdYesRequired. arXiv id of the paper, e.g. `1706.03762`. A version suffix (`v2`) is ignored: Hugging Face keeps one page per paper.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNoExtra blocks, comma-separated: `comments` and `upvoters`. Both are null without it.
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, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not mention the version-suffix normalization or the optional `include` blocks, both of which live only in the schema. Adequate but not additive.

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, front-loaded with the action and the returned payload, followed by the single hard prerequisite. No wasted wording.

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 simple single-record read with rich annotations and full schema coverage, the description covers what the tool returns and what it needs. It could note the optional `include` blocks for comments/upvoters, but nothing essential is missing.

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 arxivId, include, context, llm_model and conversation_id is already documented in the schema. The description only restates that arxivId is required, adding no new meaning; 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 ('Get a Hugging Face paper') and names the returned fields (authors, abstract, upvotes), which lets an agent distinguish it from list/search siblings. It does not explicitly contrast with hugging_face_papers_content_get or hugging_face_papers_search, so it stops short of a 5.

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

Usage Guidelines2/5

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

The only usage signal is the prerequisite 'Requires `arxivId`'. There is no statement of when to prefer this over the sibling search or content tools, and no exclusions or alternative routing.

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