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 by MyAnimeList ID, including headline, date, author, and excerpt. Answers "what's new or any announcements" questions, with optional SFW filtering.

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

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-20000).
`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

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.11.0Oct 25, 2026

changedInput schema / properties / page / description

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

changedInput schema / properties / page / maximum
```
Previous value: -1000New value: +20000
```

changedOutput schema / properties / results / items / properties / date / pattern

Previous 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)))$"New 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)))$"

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.6/5.0

Behavior4/5

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

Annotations already cover read-only and open-world, so the description adds non-obvious empirical behavior: sfw/sfw_strict filtering 'can cut the result down sharply (not necessarily to zero) rather than being a no-op.' That is genuine context beyond the schema. It's slightly redundant with the sfw/sfw_strict schema text, keeping it off a 5.

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 what it returns, then usage, then the sibling alternative, then the sfw caveat. Each sentence carries information, though the sfw sentence is long and partly retreads schema text.

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?

Output schema exists, so return values needn't be explained, yet the description still previews the fields. Combined with the mal_id sourcing hint, sibling routing, and filter caveat, an agent has everything needed to invoke this correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description still adds value by framing the id as a MAL id sourced from search_anime and by characterizing the real-world effect of the sfw flags, which the schema states only as a rule, not as an outcome.

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+resource+scope: 'List recent news articles about an anime (by mal_id)' and enumerates returned fields (headline, date, author, excerpt). It is clearly separable from get_news and get_manga_news without opening any schema.

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 the question shape it answers ('what's new / any announcements'), names the prerequisite path ('Get the mal_id from search_anime'), and explicitly routes to the alternative get_news for site-wide feeds. When-to-use and when-not-to-use are both covered.

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

Deploy Server