MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get manga recommendations

get_manga_recommendations

Read-only

Get community recommendations for manga similar to a given MyAnimeList ID, ranked by votes and capped at 25. Use it to discover related titles and optionally filter adult or Ecchi entries.

Instructions

Get community recommendations for manga similar to the given mal_id, ordered by votes and capped at the top 25 (no pagination). Get the mal_id from search_manga. Use get_top_manga instead for a global popularity/score ranking not tied to one title, or get_recent_manga_recommendations for a site-wide feed of recommendation pairs not tied to this title either. sfw/sfw_strict filter NSFW entries out of the recommendation list itself. If Tenrai is unavailable and MAL_CLIENT_ID is set, transparently retries via the official API's own recommendations field (same output shape, but at most 10 entries, ordering may differ from Tenrai's, and sfw/sfw_strict are ignored entirely).

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.
`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
`recommendations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.9.0Jul 30, 2026

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 / recommendations / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
addedOutput schema / properties / recommendations / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
changedOutput schema / properties / recommendations / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
addedOutput schema / properties / recommendations / items / properties / votes / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / recommendations / items / properties / votes / minimum
```
Added value: +0
```
changedOutput schema / properties / recommendations / items / properties / votes / type
```
Previous value: -"number"New value: +"integer"
```
addedOutput schema / properties / recommendations / items / required
```
Added value: +[
+  "mal_id"
+]
```

Changed1 schema field changedv0.8.0Jul 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedv0.7.1Jul 22, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "recommendations": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "mal_id": {
+            "type": "number"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "votes": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "recommendations"
+  ],
+  "type": "object"
+}

Addedv0.2.0Jun 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only declare read-only and open-world behavior, while the description adds the 25-entry cap, no pagination, vote ordering, NSFW filtering of the recommendation list, and a detailed fallback path with changed entry count, possible ordering differences, and ignored sfw flags. This is substantial context beyond the annotations.

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?

Front-loads the core purpose and cap, then efficiently covers id sourcing, sibling alternatives, filtering, and fallback behavior. Every sentence carries operational information without filler.

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 read-only lookup with annotations and an output schema, the description covers selection guidance, parameter sourcing, filtering semantics, result cap, and degraded-mode behavior. Nothing material is missing.

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% and the sfw fields are already well documented, so baseline is 3. The description adds where to get mal_id, clarifies that filtering applies to the recommendation list itself, and notes that fallback ignores sfw/sfw_strict.

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, including scope, vote ordering, and the top-25 cap. It explicitly distinguishes itself from get_top_manga and get_recent_manga_recommendations, so an agent can select it confidently among siblings.

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?

Explicitly tells the agent to obtain mal_id from search_manga and names two alternatives with the conditions that select them. It also clarifies sfw filtering behavior and when the official API fallback applies.

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

Deploy Server