Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face daily papers

hugging_face_papers_daily_list
Read-onlyIdempotent

Retrieve Hugging Face daily papers for a specific day, week, or month, filtered by submitter and sorted by publish date or trending, to track new AI research.

Instructions

List the papers on the Hugging Face daily papers list for a day, week or month. Optional inputs: date, week, month, sort, submitter and 2 more. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_papers_daily_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoA day, `YYYY-MM-DD`. Not later than today (UTC). Use one of `date`, `week` or `month`.
pageNoPage number (1-based). Default: 1.
sortNo`publishedAt` (default) or `trending`.
weekNoAn ISO week, `YYYY-Www` from `W01` to `W52`, e.g. `2026-W44`. Use one of `date`, `week` or `month`.
limitNoItems per page, 1-100. A page can hold fewer. Default: 50.
monthNoA month, `YYYY-MM`. Use one of `date`, `week` or `month`.
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.
submitterNoOnly papers this account put on the daily list.
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.5/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 fully covered without description help. The description adds a pagination behavior ("use page when paginated") and notes the result is a list, which is useful beyond annotations, but it does not disclose default page size behavior, result ordering, or how large a result set can be.

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?

Two short sentences with the core capability front-loaded and the return/pagination note trailing appropriately. The only blemish is the sloppy "and 2 more" enumeration, which is imprecise given the actual parameter count and costs a point against an otherwise clean structure.

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 list tool with a fully documented ten-parameter schema and no output schema, the description covers what the tool returns (a list) and how to page through it, which is the main thing an agent needs that the schema does not say. The remaining gap is that it never acknowledges the two required parameters (context, llm_model) or the conversation_id handshake, though all three are fully described in the schema.

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 the baseline is 3 and the schema already documents patterns, enums, defaults and the date/week/month exclusivity rule. The description only re-lists parameter names and then miscounts with "and 2 more" (there are eight optional params, five of which are named), adding no semantics and slightly muddying the picture.

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 papers on the Hugging Face daily papers list") plus the scope granularity ("for a day, week or month"), which is enough to distinguish it from a general papers search or single-paper fetch. It stops short of naming any sibling (e.g. hugging_face_papers_search) to contrast with, so differentiation is inferred rather than stated.

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 "for a day, week or month" implies the date/week/month selection model, and "use page when paginated" gives one operational hint. However, there is no guidance on when to pick this over hugging_face_papers_search or hugging_face_papers_get, and no note on what happens when multiple period params are supplied (the schema says "Use one of" but the description does not reinforce or explain it).

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