mcp-animenewsnetwork

List recent or browse alphabetically

list_recent

Read-onlyIdempotent

List recently added anime, manga, people, or companies from the Anime News Network encyclopedia. Specify a starting letter to browse titles alphabetically, or fetch IDs for further details.

Instructions

List what was added to the Anime News Network encyclopedia most recently: anime, manga, people or companies. Pass 'starts_with' to browse titles alphabetically instead, which only applies to anime and manga. Rows carry an id you can pass to get_title when the kind is anime or manga. This is a listing, not a search: use search_titles when you know what you are looking for.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	Which catalogue to list.	anime
`limit`	No	How many rows to return.
`offset`	No	How many rows to skip, for paging.
`starts_with`	No	Single letter. Switches to an alphabetical browse of titles. Anime and manga only.

Output Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes
`mode`	Yes	'recent' is by date added, 'browse' is alphabetical.
`rows`	Yes
`notes`	Yes
`offset`	Yes
`next_offset`	Yes	Pass as 'offset' for the next page. Null when the last page came back short.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv2.0.0Aug 26, 2026

addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```

changedOutput schema / properties / next_offset / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / offset / minimum
```
Added value: +-9007199254740991
```

addedOutput schema / properties / rows / items / properties / date_added / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / rows / items / properties / date_added / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

changedOutput schema / properties / rows / items / properties / id / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / rows / items / properties / precision / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / rows / items / properties / precision / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / rows / items / properties / source_url / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / rows / items / properties / source_url / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / rows / items / properties / type / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / rows / items / properties / type / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / rows / items / properties / vintage / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / rows / items / properties / vintage / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

First observedv1.0.0Aug 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds complementary context: starts_with switches to alphabetical browsing restricted to anime/manga, and returned rows expose an id consumable by get_title. No hidden side effects or usage restrictions are omitted.

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?

Three tight sentences front-load the core purpose, then add the browse mode, id usage, and a clear search alternative. No filler or duplicated schema content.

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?

With an output schema present, return details don't need to be repeated. The description covers what the tool lists, how to switch modes, the kind restrictions, and how rows connect to a sibling tool, which is everything an agent needs to select and call it appropriately.

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?

The Schema Description Coverage is 100%, so the schema fully documents kind, limit, offset, and starts_with, including defaults and constraints. The description mostly restates starts_with's behavior rather than adding new parameter-specific meaning, so the baseline 3 is appropriate.

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?

Description states the exact operation: listing what was recently added to the ANN encyclopedia, with the four supported kinds enumerated. It distinguishes itself from a search and explicitly contrasts with search_titles, making the tool's job unambiguous.

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

Usage Guidelines5/5

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

Gives explicit direction on when to use the tool ('listing, not a search') and names the alternative (search_titles) for when a specific entry is sought. It also explains the alternative browse mode via starts_with and refers the returned id to get_title.

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

Deploy Server