MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get manga news

get_manga_news

Read-only

Fetch recent news articles for a specific manga by MyAnimeList ID, including headlines, dates, authors, and excerpts to answer what's new or announcement questions.

Instructions

List recent news articles about a manga (by mal_id): headline, date, author and excerpt. Useful for 'what's new / any announcements' questions. Get the mal_id from search_manga. Use get_news instead for a site-wide feed not tied to one manga. sfw/sfw_strict filter out articles for an NSFW/adult-adjacent manga — 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)))$"

Addedv0.9.0Jul 30, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds non-obvious behavioral context: that sfw/sfw_strict filtering can sharply reduce results rather than being a no-op, which was 'verified live'. Pagination behavior is left to the schema, so not quite 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 verb, resource, and return fields in the first sentence, then routing guidance and the filtering caveat. Dense and nearly waste-free, though the sfw nuance sentence is lengthy.

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 a full output schema, 100% parameter coverage, and clear sibling routing, the description supplies everything an agent needs to call this correctly, including the id source and the filter caveat.

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% with rich per-parameter descriptions, so the baseline is 3. The description goes beyond by characterizing the real-world effect of sfw/sfw_strict filtering (sharp reduction, not necessarily zero), adding meaning the schema doesn't convey.

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 ('List recent news articles about a manga') plus the exact fields returned (headline, date, author, excerpt). It explicitly distinguishes itself from the get_news sibling for site-wide feeds, so an agent can pick it without opening the 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?

Says it's for 'what's new / any announcements' questions, directs the agent to obtain the mal_id from search_manga, and names the alternative (get_news) with the condition that selects it. When-to-use, prerequisite sourcing, and exclusion are all explicit.

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

Deploy Server