mcp-animenewsnetwork

Read the news wire

get_news

Read-onlyIdempotent

Retrieve Anime News Network stories from RSS feeds, choosing all, news, or reviews plus category, limit, and edition filters to surface relevant articles for reading or citation.

Instructions

Read the latest Anime News Network stories from their RSS feeds. 'all' mixes news, reviews and features; 'news' and 'reviews' are the narrower feeds. Filter with 'category' to keep only stories the feed tags a given way, such as Manga or Anime. The feed is the whole window available: there is no way to reach older stories through this tool. When you repeat a story, cite Anime News Network and link the article.

Input Schema

Name	Required	Description	Default
`feed`	No	Which feed to read. 'all' is the busiest.	all
`limit`	No	How many stories to return.
`edition`	No	Regional edition. They differ mostly in release and licensing coverage.	us
`category`	No	Keep only items tagged this way, matched case-insensitively.

Output Schema

Name	Required	Description
`feed`	Yes
`items`	Yes
`notes`	Yes
`edition`	Yes
`total_available`	Yes	Items in the feed after 'category' was applied, before 'limit'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv3.0.0Oct 30, 2026

addedInput schema / properties / category / minLength
```
Added value: +1
```

addedOutput schema / properties / items / items / properties / categories

Added value: +{
+  "description": "Every tag the feed carries on the story. Empty when it carries none.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / items / items / properties / category

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / items / items / properties / published_at / anyOf

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

addedOutput schema / properties / items / items / properties / published_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / items / items / properties / summary / anyOf

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

addedOutput schema / properties / items / items / properties / summary / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / items / items / required

Previous value: -[
-  "title",
-  "link",
-  "summary",
-  "published_at",
-  "category"
-]New value: +[
+  "title",
+  "link",
+  "summary",
+  "published_at",
+  "categories"
+]

Changed8 schema fields changedv2.0.0Aug 26, 2026
- addedOutput schema / properties / items / items / properties / category / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / category / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / published_at / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / published_at / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / summary / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / summary / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / total_available / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / total_available / minimum
```
Added value: +-9007199254740991
```
First observedv1.0.0Aug 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds genuinely new behavioral facts: the feed is a bounded window with no older-story access, feed composition, and a citation obligation for reuse — none of which appear in the structured fields.

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?

Front-loaded with purpose, then feed semantics, then the hard window limit. Every sentence carries information; the closing citation instruction is a usage policy rather than tool semantics but is short enough not to be bloat.

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?

With an output schema and rich annotations, the description only needs to cover scope and limits, which it does. The one missing piece is routing to a sibling for older or search-based retrieval, which it gestures at only implicitly.

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 coverage is 100%, so the schema already documents all four parameters including enums. The description adds some semantic color for 'feed' (what 'all' mixes) and a case example for 'category', but says nothing about 'limit' or 'edition' beyond the schema — baseline 3 applies.

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?

States a specific verb and resource ('Read the latest Anime News Network stories from their RSS feeds') and immediately unpacks what each feed contains. An agent can distinguish this from search_titles/get_title/list_recent based on the live-RSS scope described.

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?

Gives concrete selection guidance between feed values and explains when to use 'category'. It also implicitly excludes the tool for historical lookups ('no way to reach older stories through this tool'), though it does not name which sibling to use instead.

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

Deploy Server