MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get manga reviews

get_manga_reviews

Read-only

Fetch MyAnimeList user reviews for a manga by MAL ID, including scores, spoiler flags, chapters read, and community reactions. Use filters, sorting, and pagination to find relevant reviews.

Instructions

Get user reviews for one manga (by mal_id): review text (truncated to 1200 characters), score, spoiler/preliminary flags, chapters read at review time (chapters_read, not episodes_watched — that field is anime-only), and community reaction counts. limit (default 5) caps how many of the fetched page's reviews come back — it does not itself fetch further pages, use page for Tenrai's own ~20-per-page listing. sort/preliminary/spoilers/sentiment filter/order the underlying set before that cap is applied. Get the mal_id from search_manga.

Input Schema

Name	Required	Description
`id`	Yes	MyAnimeList numeric ID.
`page`	No	1-based page number for pagination (1-20000).
`sort`	No	Sort order. Defaults to most_helpful (Tenrai's own default) when omitted.
`limit`	No	How many of the page's reviews to return (1-20; a page holds 20).
`spoilers`	No	Filter by spoiler. 'true' includes them alongside other reviews, 'false' (default) excludes them, 'only' returns exclusively spoiler reviews.
`sentiment`	No	Restrict to reviews with this overall sentiment tag. Omit for all sentiments.
`preliminary`	No	Filter by preliminary. 'true' includes them alongside other reviews, 'false' (default) excludes them, 'only' returns exclusively preliminary reviews.

Output Schema

Name	Required	Description	Default
`page`	Yes
`reviews`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.11.0Oct 25, 2026

changedInput schema / properties / limit / description

Previous value: -"Max results per page (1-50)."New value: +"How many of the page's reviews to return (1-20; a page holds 20)."

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

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
```

changedInput schema / properties / preliminary / description

Previous value: -"Filter by preliminary. 'true' includes them alongside other reviews (default), 'false' excludes them, 'only' returns exclusively preliminary reviews."New value: +"Filter by preliminary. 'true' includes them alongside other reviews, 'false' (default) excludes them, 'only' returns exclusively preliminary reviews."

changedInput schema / properties / spoilers / description

Previous value: -"Filter by spoiler. 'true' includes them alongside other reviews (default), 'false' excludes them, 'only' returns exclusively spoiler reviews."New value: +"Filter by spoiler. 'true' includes them alongside other reviews, 'false' (default) excludes them, 'only' returns exclusively spoiler reviews."

addedOutput schema / properties / page

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "current_page": {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "has_next_page": {
+      "type": "boolean"
+    },
+    "last_visible_page": {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "total": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

changedOutput schema / properties / reviews / 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)))$"

changedOutput schema / required

Previous value: -[
-  "reviews"
-]New value: +[
+  "reviews",
+  "page"
+]

Changed17 schema fields changedv0.9.0Jul 30, 2026

changedInput schema / properties / limit / description

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

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

addedInput schema / properties / page

Added value: +{
+  "description": "1-based page number for pagination (1-1000).",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / preliminary

Added value: +{
+  "description": "Filter by preliminary. 'true' includes them alongside other reviews (default), 'false' excludes them, 'only' returns exclusively preliminary reviews.",
+  "enum": [
+    "true",
+    "false",
+    "only"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sentiment

Added value: +{
+  "description": "Restrict to reviews with this overall sentiment tag. Omit for all sentiments.",
+  "enum": [
+    "recommended",
+    "mixed_feelings",
+    "not_recommended"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "Sort order. Defaults to most_helpful (Tenrai's own default) when omitted.",
+  "enum": [
+    "newest",
+    "oldest",
+    "most_helpful"
+  ],
+  "type": "string"
+}

addedInput schema / properties / spoilers

Added value: +{
+  "description": "Filter by spoiler. 'true' includes them alongside other reviews (default), 'false' excludes them, 'only' returns exclusively spoiler reviews.",
+  "enum": [
+    "true",
+    "false",
+    "only"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / reviews / items / properties / chapters_read

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / reviews / items / properties / date / format
```
Added value: +"date-time"
```

addedOutput schema / properties / reviews / 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 / reviews / items / properties / episodes_watched

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / reviews / items / properties / is_preliminary
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / reviews / items / properties / is_spoiler
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / reviews / items / properties / reactions

Added value: +{
+  "additionalProperties": {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / reviews / items / properties / score / maximum
```
Added value: +10
```
addedOutput schema / properties / reviews / items / properties / score / minimum
```
Added value: +1
```
changedOutput schema / properties / reviews / items / properties / score / type
```
Previous value: -"number"New value: +"integer"
```

Changed2 schema fields changedv0.8.0Jul 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / limit / default
```
Added value: +5
```

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": {
+    "reviews": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "review": {
+            "type": "string"
+          },
+          "score": {
+            "type": "number"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "type": "string"
+          },
+          "user": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "tags"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "reviews"
+  ],
+  "type": "object"
+}

Addedv0.2.0Jun 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries most of the burden and does well: it discloses the 1200-character truncation of review text, that `limit` caps the already-filtered page rather than triggering new fetches, and that Tenrai lists roughly 20 per page. It says nothing about auth needs, rate limits, or error behavior, so it is strong but not exhaustive.

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 the resource and identifier, then the pagination/cap mechanics, then the id-sourcing pointer. Dense with parenthetical asides, but each one (truncation length, chapters_read caveat, 20-per-page) is load-bearing rather than 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?

With an output schema handling return shape and annotations covering safety, the description fills the remaining gaps: identifier source, pagination model, filter-before-cap ordering, and truncation. An agent has everything needed to call this correctly on the first try.

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 a 3 would be the floor, but the description adds real meaning the schema does not: filters and sort are applied before `limit` truncates the result, and `page` is tied to a ~20-per-page listing model. That ordering detail is exactly the kind of clarification a schema cannot express.

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 ('Get user reviews for one manga') and scopes it by mal_id. It also distinguishes itself from the anime counterpart by explicitly noting `chapters_read` versus `episodes_watched` being anime-only, so an agent can separate it from get_anime_reviews 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tells the agent where to source the identifier ('Get the mal_id from search_manga') and clarifies the limit-versus-page relationship, which is the main misuse risk here. It stops short of naming get_anime_reviews as the alternative for anime, leaving that routing to inference from the chapters_read remark.

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

Deploy Server