MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get anime/manga news

get_news

Read-only

Retrieve site-wide MyAnimeList news articles with headlines, dates, authors, and excerpts; search by keyword or filter by topic tag, and optionally exclude adult or ecchi content.

Instructions

List recent MyAnimeList news articles site-wide (headline, date, author, excerpt) — not tied to one anime or manga. Use q to search by keyword or tag to filter by topic tag. Use get_anime_news/get_manga_news instead for news about one specific anime/manga by mal_id. sfw/sfw_strict drop articles about adult content.

Input Schema

Name	Required	Description
`q`	No	Search query, e.g. a keyword or title. Verified live to search beyond just the headline (a real, unfamiliar-sounding title can still match) — don't assume a result's title visibly contains the term.
`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.
`tag`	No	Filter by topic tag.
`page`	No	1-based page number for pagination (1-20000).
`limit`	No	Max results per page (1-100).
`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.

Changed10 schema fields changedv0.11.0Oct 25, 2026

changedInput schema / properties / limit / description

Previous value: -"Max results per page (1-50)."New value: +"Max results per page (1-100)."

changedInput schema / properties / limit / maximum
```
Previous value: -50New value: +100
```

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
```
addedInput schema / properties / q / maxLength
```
Added value: +300
```
addedInput schema / properties / q / minLength
```
Added value: +1
```

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"
+}

addedInput schema / properties / tag / maxLength
```
Added value: +300
```

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

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context — that results are site-wide rather than entity-scoped, and that sfw/sfw_strict drop adult-content articles — but the sfw semantics largely duplicate the schema text and nothing is said about pagination limits or result-set size.

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: scope first, then filtering, then sibling routing, then the sfw caveat. No filler, and the most disambiguating information (site-wide vs entity-scoped) is front-loaded.

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 present, the description needn't explain return fields, and it correctly avoids that. It covers scope, routing and filtering, but leaves pagination behavior (page/limit defaults) entirely to the schema, a minor gap for a paginated list endpoint.

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 description coverage is 100%, so all six parameters are already documented in detail (including the sfw vs sfw_strict nuance). The description's mention of q and tag restates what the schema says rather than adding new semantics; baseline 3 is appropriate when the schema does the heavy lifting.

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 MyAnimeList news articles") plus the fields returned and the site-wide scope. It explicitly contrasts with get_anime_news/get_manga_news, so an agent can distinguish it from siblings without opening a 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 explicit routing: use q for keyword search, tag for topic filtering, and the sfw/sfw_strict pair for content filtering. It names the two sibling tools to use instead when the request is scoped to one anime or manga by mal_id, which is exactly the when-not guidance an agent needs.

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

Deploy Server