Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Hugging Face papers

hugging_face_papers_search
Read-onlyIdempotent

Search Hugging Face papers by keyword or list the newest publications; use cursor pagination to browse result pages.

Instructions

Search Hugging Face papers by keyword, or list the newest papers. Optional inputs: query, limit and cursor. Returns a list (use cursor 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_papers_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1-100. A page can hold fewer. Default: 50.
queryNoSearch text. Without it the endpoint lists the newest papers. A search returns up to 120 papers and has no further pages.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep every other parameter the same.
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

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so safety and idempotency are covered structurally. The description adds only that the result is a list and that a cursor is used when paginated; it does not disclose rate limits, result ordering, or the fact that keyword searches are capped and cannot be paged (that detail lives only in the schema).

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 primary capability and followed by the parameter/pagination note. There is no filler and nothing repeated from the title.

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 search/list tool with full schema coverage and no output schema, the description covers purpose, both modes, and pagination adequately. It could go further by clarifying the search-result cap or how it differs from the daily-list sibling, 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 is already documented in the schema, which sets the baseline at 3. The description names query, limit and cursor but adds no semantics beyond the schema and omits the required analytics parameters (context, llm_model) and conversation_id entirely.

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 ('Search Hugging Face papers by keyword') and adds the second mode ('or list the newest papers'), so the dual behaviour is clear. It does not distinguish itself from nearby siblings such as hugging_face_papers_daily_list, hugging_face_papers_get, or hugging_face_search_fulltext, leaving the agent to infer the boundaries.

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?

It implies when each mode applies by pairing 'query' with search and its absence with 'list the newest papers', and it hints at pagination via the cursor. However, it never explicitly says when to prefer this over papers_daily_list (also a newest-papers listing) or papers_get, so the routing guidance is only implied.

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