MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get recent manga recommendations

get_recent_manga_recommendations

Read-only

Fetch a site-wide feed of recently submitted manga recommendation pairs with user commentary, letting you discover what to read next from community suggestions rather than a specific title.

Instructions

Get a site-wide feed of recently-submitted manga recommendation pairs (e.g. 'if you liked X, try Y') with the submitting user's own commentary — not tied to any one title. Use get_manga_recommendations instead for recommendations similar to a specific mal_id. No official-API fallback exists for this tool — it always needs Tenrai itself to be reachable.

Input Schema

Name	Required	Description
`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).
`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.

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.5/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 the safety profile is covered. The description adds meaningful behavioral context beyond that: the feed includes submitting users' commentary, it is not title-scoped, and it has no official-API fallback so it depends on Tenrai availability. It stops short of describing pagination or ordering behavior, but that is largely schema-handled.

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 sentences, front-loaded with the core purpose, followed by the sibling alternative and the operational caveat. No repetition or filler, and the most decision-relevant information appears first.

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?

The description covers purpose, scope, sibling differentiation, and the lack of an official-API fallback. With an output schema present and full parameter documentation in the input schema, nothing essential is missing for an agent to select and invoke this tool correctly.

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%, and the schema itself carefully documents sfw, sfw_strict, page, and limit, including the subtle distinction between sfw and sfw_strict. The description adds no parameter-level detail, so the baseline 3 is appropriate when the schema carries the full burden.

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 ('Get a site-wide feed of recently-submitted manga recommendation pairs'), clarifies the content ('with the submitting user's own commentary'), and explicitly scopes it as 'not tied to any one title'. This cleanly separates it from get_manga_recommendations, which is title-specific.

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 explicitly routes the agent: use this for a site-wide feed, but use get_manga_recommendations for recommendations similar to a specific mal_id. It also states a critical condition — no official-API fallback exists, so Tenrai must be reachable — which is exactly the kind of when/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