Paperswithcode

Trending Papers

trending_papers

Read-onlyIdempotent

Today's trending ML/AI papers (or a given day's), ranked by community upvotes, via Hugging Face Papers. Use for "what are the hot AI papers", "trending ML research", "top papers this week".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Optional day YYYY-MM-DD (default: latest).
`limit`	No	Max papers to return (1-50, default 15).

Output Schema

TableJSON Schema

Name	Required	Description
`date`	No
`count`	No
`papers`	No	Array of formatted paper objects

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed18 schema fields changedJul 2, 2026

addedOutput schema / properties / count
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / date
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / papers / items / properties / abstract

Removed value: -{
-  "description": "Paper abstract",
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedOutput schema / properties / papers / items / properties / arxiv_id / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```

removedOutput schema / properties / papers / items / properties / conference

Removed value: -{
-  "description": "Conference name",
-  "type": [
-    "string",
-    "null"
-  ]
-}

addedOutput schema / properties / papers / items / properties / github_repo
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

removedOutput schema / properties / papers / items / properties / id

Removed value: -{
-  "description": "Papers With Code paper ID",
-  "type": "string"
-}

removedOutput schema / properties / papers / items / properties / proceeding

Removed value: -{
-  "description": "Proceeding identifier",
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedOutput schema / properties / papers / items / properties / published / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```
changedOutput schema / properties / papers / items / properties / title / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```
addedOutput schema / properties / papers / items / properties / upvotes
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / papers / items / properties / url
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / papers / items / properties / url_abs

Removed value: -{
-  "description": "URL to paper abstract",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / papers / items / properties / url_pdf

Removed value: -{
-  "description": "URL to paper PDF",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / papers / items / required

Removed value: -[
-  "id",
-  "arxiv_id",
-  "title",
-  "abstract",
-  "authors",
-  "published",
-  "conference",
-  "proceeding",
-  "url_abs",
-  "url_pdf"
-]

removedOutput schema / properties / returned

Removed value: -{
-  "description": "Number of papers returned in this response",
-  "type": "number"
-}

removedOutput schema / properties / total

Removed value: -{
-  "description": "Total number of trending papers",
-  "type": "number"
-}

removedOutput schema / required

Removed value: -[
-  "total",
-  "returned",
-  "papers"
-]

Changed3 schema fields changedJun 25, 2026

addedInput schema / properties / date

Added value: +{
+  "description": "Optional day YYYY-MM-DD (default: latest).",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Number of results to return (default: 10, max: 50)"New value: +"Max papers to return (1-50, default 15)."

addedInput schema / required
```
Added value: +[]
```

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "papers": {
+      "description": "Array of formatted paper objects",
+      "items": {
+        "properties": {
+          "abstract": {
+            "description": "Paper abstract",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "arxiv_id": {
+            "description": "ArXiv ID of the paper",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "authors": {
+            "description": "List of paper authors",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "conference": {
+            "description": "Conference name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Papers With Code paper ID",
+            "type": "string"
+          },
+          "proceeding": {
+            "description": "Proceeding identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "published": {
+            "description": "Publication date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Paper title",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url_abs": {
+            "description": "URL to paper abstract",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url_pdf": {
+            "description": "URL to paper PDF",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "arxiv_id",
+          "title",
+          "abstract",
+          "authors",
+          "published",
+          "conference",
+          "proceeding",
+          "url_abs",
+          "url_pdf"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of papers returned in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of trending papers",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "papers"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "limit": 15
+  }
+]
```
First observedApr 22, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the source (Hugging Face) and ranking method (community upvotes), which is useful but minimal. It does not disclose update frequency, cache behavior, or pagination, but given annotations, the description adequately supplements without contradiction.

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?

The description is two sentences: first defines the tool and source, second gives common use cases. It is front-loaded with the core action and wastes no words. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema (so return values are documented elsewhere), only two simple optional parameters, and no complex behavior, the description provides sufficient context: what the tool does, where data comes from, and when to use it. No important information 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 the baseline is 3. The description does not add any parameter-specific details beyond what the schema already provides (date and limit). The example 'limit: 15' in the schema is helpful, but the description adds no extra semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool returns today's or a given day's trending ML/AI papers ranked by community upvotes via Hugging Face Papers. It gives specific example queries that distinguish it from sibling tools like get_paper (specific paper) and search_papers (search by query). The verb 'trending' and resource 'papers' are precise.

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

Usage Guidelines4/5

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

The description explicitly provides usage scenarios (e.g., 'what are the hot AI papers', 'top papers this week'), making it clear when to use this tool. However, it does not explicitly exclude cases where other tools like search_papers or get_paper would be more appropriate, leaving a minor gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Paperswithcode tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation2/5

Several tools form overlapping families: ask_pipeworx and ask_pipeworx_beta are currently identical, ask_pipeworx_grounded and deep_research cover much of the same router territory, and five Polymarket tools overlap heavily on edge/arbitrage analysis. The descriptions are detailed, but an agent would regularly need to compare multiple near-equivalent candidates before choosing one.

Naming Consistency3/5

Names are consistently snake_case and readable, but the conventions vary widely: verb_noun (search_papers, resolve_entity), noun phrases (entity_profile, polymarket_arbitrage, recent_changes), bare verbs (remember, subscribe, forget), and suffixed variants (ask_pipeworx_beta, ask_pipeworx_grounded). It is not chaotic, but there is no single predictable pattern.

Tool Count2/5

Thirty-five tools is far too many for a server named Paperswithcode, especially since only four tools actually relate to papers while the rest cover data routing, prediction markets, memory, subscriptions, npm auditing, llms.txt generation, and AI visibility. The count feels bloated and the scope unfocused relative to the server's apparent identity.

Completeness3/5

The paper-discovery subdomain is reasonably covered with search, trending, detail, and implementation lookup, and the broader set includes discovery, memory, subscription lifecycle, and feedback tools. However, the overall surface is a patchwork of unrelated domains with no well-defined boundary, and paper datasets/models can only be counted rather than directly listed. Agents can work around most gaps, but the coverage is uneven.

Trending Papers

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources