MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get anime news

get_anime_news

Read-only

Retrieve recent news articles for a specific anime using its MyAnimeList ID, including headline, date, author, and excerpt. Use this to answer questions about announcements or updates for one show.

Instructions

List recent news articles about an anime (by mal_id): headline, date, author and excerpt. Useful for 'what's new / any announcements' questions. Get the mal_id from search_anime. Use get_news instead for a site-wide feed not tied to one anime. sfw/sfw_strict filter out articles for an NSFW/adult-adjacent anime — verified live this can cut the result down sharply (not necessarily to zero) rather than being a no-op.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	MyAnimeList numeric ID.
`sfw`	No	If true, exclude adult/explicit-rated entries (R+ Mild Nudity and up). Defaults to false (no filtering). Note: this alone still allows mainstream, safely-rated shows tagged with the Ecchi genre (fanservice) through — use `sfw_strict` to also exclude those.
`page`	No	1-based page number for pagination (1-1000).
`sfw_strict`	No	If true, exclude adult/explicit-rated entries AND anything tagged with the Ecchi genre, even otherwise-mainstream/safely-rated shows. Stricter than `sfw` alone. Defaults to false.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedv0.9.0Jul 30, 2026

changedInput schema / properties / page / description

Previous value: -"1-based page number for pagination."New value: +"1-based page number for pagination (1-1000)."

changedInput schema / properties / page / maximum

Previous value: -9007199254740991New value: +1000

addedInput schema / properties / sfw

Added value: +{
+  "description": "If true, exclude adult/explicit-rated entries (R+ Mild Nudity and up). Defaults to false (no filtering). Note: this alone still allows mainstream, safely-rated shows tagged with the Ecchi genre (fanservice) through — use `sfw_strict` to also exclude those.",
+  "type": "boolean"
+}

addedInput schema / properties / sfw_strict

Added value: +{
+  "description": "If true, exclude adult/explicit-rated entries AND anything tagged with the Ecchi genre, even otherwise-mainstream/safely-rated shows. Stricter than `sfw` alone. Defaults to false.",
+  "type": "boolean"
+}

addedOutput schema / properties / page / properties / current_page / exclusiveMinimum
```
Added value: +0
```
addedOutput schema / properties / page / properties / current_page / maximum
```
Added value: +9007199254740991
```
changedOutput schema / properties / page / properties / current_page / type
```
Previous value: -"number"New value: +"integer"
```
addedOutput schema / properties / page / properties / last_visible_page / exclusiveMinimum
```
Added value: +0
```
addedOutput schema / properties / page / properties / last_visible_page / maximum
```
Added value: +9007199254740991
```
changedOutput schema / properties / page / properties / last_visible_page / type
```
Previous value: -"number"New value: +"integer"
```
addedOutput schema / properties / page / properties / total / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / page / properties / total / minimum
```
Added value: +0
```
changedOutput schema / properties / page / properties / total / type
```
Previous value: -"number"New value: +"integer"
```
addedOutput schema / properties / results / items / properties / comments / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / results / items / properties / comments / minimum
```
Added value: +0
```
changedOutput schema / properties / results / items / properties / comments / type
```
Previous value: -"number"New value: +"integer"
```
addedOutput schema / properties / results / items / properties / date / format
```
Added value: +"date-time"
```

addedOutput schema / properties / results / items / properties / date / pattern

Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"

addedOutput schema / properties / results / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
addedOutput schema / properties / results / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
changedOutput schema / properties / results / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```

Addedv0.8.0Jul 29, 2026
Removedv0.7.1Jul 22, 2026
Addedv0.2.0Jun 29, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already mark this as safe and open, and the description adds a useful behavioral caveat beyond them: sfw/sfw_strict filters 'can cut the result down sharply (not necessarily to zero)' rather than being a no-op. This sort of verified edge behavior is exactly the context an agent needs.

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 three compact sentences with no filler. It front-loads the core behavior, then gives routing context, provenance, and a critical sfw-filter caveat, each earning 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?

For a simple read-only list tool, the description covers purpose, input source, alternative tools, and subtle filter behavior. The output schema exists to describe return values, so the description does not need to repeat them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers all four parameters at 100%, so the description does not need to repeat them. It still adds meaningful parameter guidance by explaining how to obtain the mal_id and by warning about the practical impact of the sfw flags, which goes beyond the schema text.

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 names a specific verb and resource: 'List recent news articles about an anime (by mal_id)' with the headline, date, author, and excerpt output. It also distinguishes itself from the site-wide get_news alternative, so an agent understands exactly what this tool is for.

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?

It gives explicit when-to-use guidance: 'what's new / any announcements' questions. It also tells the agent how to get the required id from search_anime and when to choose a different tool, get_news, instead.

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

Deploy Server