MAL MCP Server

Get anime episodes

get_anime_episodes

Read-only

Retrieve an anime's episode list using the MyAnimeList ID. Get titles, air dates, and filler/recap flags with pagination for long-running 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

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`episodes`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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.0

Behavior4/5

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

Annotations already set readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond that: pagination at roughly 100 per page and the use of `page` for long-running season. It does not cover every nuance like rate limits, but for read-only list pagination this is solid additional transparency.

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?

The description is three concise sentences that each carry useful information: the operation, the pagination behavior, and the source of the identifier. It is front-loaded and contains no filler, making it ideal for an AI agent to read quickly.

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?

This is a small, simple tool with a read-only annotation, an output schema, and just two parameters. The description covers operation semantics, pagination, episode-related return values, and how to source the required id. It does not need to explain output shape because an output schema exists; only minor details like default sort order are omitted but not critical.

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?

The schema already describes both parameters: 'id' as a MyAnimeList numeric ID and 'page' as a 1-based page number. The description says 'mal_id' and 'use `page` for long-running series', which adds mild usage color but does not significantly expand parameter semantics. With 100% schema coverage, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'List an anime's episodes (by mal_id) with titles, air dates and filler/recap flags.' This clearly conveys what the tool returns. It is distinct from sibling tools like get_anime_videos or get_anime_schedule because of the focus on episodes and filler/recap flags, though it does not explicitly name those siblings.

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?

The description provides clear context: use this to fetch a specific anime's episode list, get mal_id from search_anime, and use page for long series. It does not explicitly state when *not* to use this tool or contrast it with alternatives, but the usage context is present enough to guide an agent.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grinv/mal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server