MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get my anime list

get_my_anime_list

Read-only

Retrieve your authenticated MyAnimeList anime list with each entry's status, score, and progress. Supports status filters, sorting, and pagination; requires a MyAnimeList login.

Instructions

Get the authenticated user's own anime list, with each entry's status, score and progress. Requires a MyAnimeList login.

Input Schema

Name	Required	Description
`sort`	No	Sort order. list_score/list_updated_at return highest/most-recent first; anime_title returns A-Z.
`limit`	No	Max results (1-1000).
`offset`	No	Offset for pagination.
`status`	No	List status bucket.

Output Schema

Name	Required	Description	Default
`items`	Yes
`has_next_page`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.11.0Oct 25, 2026
- changedInput schema / properties / limit / description
```
Previous value: -"Max results (1-100)."New value: +"Max results (1-1000)."
```
- changedInput schema / properties / limit / maximum
```
Previous value: -100New value: +1000
```
Changed4 schema fields changedv0.9.0Jul 30, 2026
- addedOutput schema / properties / items / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / items / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / items / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / items / items / required
```
Added value: +[
+  "mal_id"
+]
```

Changed2 schema fields changedv0.8.0Jul 29, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / sort / description

Previous value: -"Sort order."New value: +"Sort order. list_score/list_updated_at return highest/most-recent first; anime_title returns A-Z."

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": {
+    "has_next_page": {
+      "type": "boolean"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "list_status": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "mal_id": {
+            "type": "number"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "has_next_page"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 27, 2026

TDQS

A3.8/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 safety is covered. The description adds the authentication requirement ('Requires a MyAnimeList login'), which is operationally critical and not expressed in the annotations or schema. It also discloses the shape of each entry, which helps the agent decide it is the personal list rather than catalog data. That said, it says nothing about empty-list or pagination behavior.

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?

Two sentences, no waste, with the core purpose stated first and the auth precondition second. Every clause earns its place.

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?

An output schema exists, so return values need no explanation, and filtering and pagination are fully specified in the schema. The description covers purpose and auth. It is slightly thin on how the list is scoped or paginated across a large collection, but it is sufficient for correct invocation.

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 all four parameters (sort, limit, offset, status) are documented in the schema, including enum semantics and sort ordering. The description adds no parameter-level guidance, so the baseline score of 3 applies.

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?

Specific verb plus resource ('Get the authenticated user's own anime list') with the scope qualifier 'authenticated user's own', which separates it from the public catalog siblings like get_anime and search_anime. It also enumerates the returned fields (status, score, progress). It does not name get_my_manga_list as the manga counterpart, so sibling differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'Requires a MyAnimeList login' gives a useful precondition, which implies the tool is only for the logged-in user's private data. But there is no explicit statement of when to use it versus the read siblings or versus the mutation siblings update_my_anime_status and delete_my_anime_list_item. So usage must be inferred from context.

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

Deploy Server