MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get anime episodes

get_anime_episodes

Read-only

Fetch an anime's episodes by MyAnimeList ID to get titles, air dates, and filler/recap flags, with pagination for long series.

Instructions

List an anime's episodes (by mal_id) with titles, air dates and filler/recap flags. Paginated (~100 per page); use page for long-running series. Get the mal_id from search_anime.

Input Schema

Name	Required	Description	Default
`id`	Yes	MyAnimeList numeric ID.
`page`	No	1-based page number for pagination (1-20000).

Output Schema

Name	Required	Description	Default
`page`	Yes
`episodes`	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 / episodes / items / properties / aired / 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)))$"

Changed4 schema fields changedv0.10.0Aug 24, 2026
- addedOutput schema / properties / episodes / items / properties / duration
```
Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedOutput schema / properties / episodes / items / properties / image_url
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / episodes / items / properties / replies
```
Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedOutput schema / properties / episodes / items / properties / synopsis
```
Added value: +{
+  "type": "string"
+}
```
Changed16 schema fields changedv0.9.0Jul 30, 2026
- changedInput schema / properties / page / description
```
Previous value: -"1-based page number for pagination."New value: +"1-based page number for pagination (1-1000)."
```
- changedInput schema / properties / page / maximum
```
Previous value: -9007199254740991New value: +1000
```
- addedOutput schema / properties / episodes / items / properties / aired / format
```
Added value: +"date-time"
```
- addedOutput schema / properties / episodes / items / properties / aired / 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 / episodes / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / episodes / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / episodes / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / page / properties / current_page / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / page / properties / current_page / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / page / properties / current_page / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / page / properties / last_visible_page / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / page / properties / last_visible_page / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / page / properties / last_visible_page / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / page / properties / total / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / page / properties / total / minimum
```
Added value: +0
```
- changedOutput schema / properties / page / properties / total / type
```
Previous value: -"number"New value: +"integer"
```
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": {
+    "episodes": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "aired": {
+            "type": "string"
+          },
+          "filler": {
+            "type": "boolean"
+          },
+          "mal_id": {
+            "type": "number"
+          },
+          "recap": {
+            "type": "boolean"
+          },
+          "score": {
+            "type": "number"
+          },
+          "title": {
+            "type": "string"
+          },
+          "title_japanese": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "page": {
+      "additionalProperties": false,
+      "properties": {
+        "current_page": {
+          "type": "number"
+        },
+        "has_next_page": {
+          "type": "boolean"
+        },
+        "last_visible_page": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "episodes",
+    "page"
+  ],
+  "type": "object"
+}

Addedv0.2.0Jun 29, 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 and openWorldHint, so safety is covered; the description adds genuinely new behavioral context with the ~100-per-page pagination size and the presence of filler/recap flags in the results. It does not describe ordering or error behavior, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and result fields, followed by the pagination constraint and the prerequisite. No 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?

An output schema exists, so return values need no prose; with only two parameters and a full schema, the description covers everything an agent needs — what it lists, how pagination works, and where the required id comes from.

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 the baseline is 3; the description goes further by explaining that `page` exists specifically for long-running series and that `id` is a MyAnimeList ID obtained from search_anime, adding meaning beyond the schema's terse field docs.

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 an anime's episodes') and enumerates the fields returned (titles, air dates, filler/recap flags). It is clearly distinguishable from get_anime (details) and from search_anime, which is named as the way to obtain the id.

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?

Explicitly routes the agent to search_anime for the mal_id and tells it to use `page` for long-running series. No explicit when-not guidance versus get_anime, but the usage context is unambiguous.

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

Deploy Server