MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get my manga list

get_my_manga_list

Read-only

Fetch the authenticated user's manga list with status, score, and reading progress, with options to filter by status, sort, and paginate.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_manga_list"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort order. list_score/list_updated_at return highest/most-recent first; manga_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
```

Changed1 schema field changedv0.10.0Aug 24, 2026

changedInput schema / properties / sort / description

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

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"
+]
```
Addedv0.8.0Jul 29, 2026
Removedv0.7.1Jul 22, 2026
First observedv0.1.0Jun 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-dependency profile is covered. The description adds one genuinely useful behavioral fact beyond annotations: a MyAnimeList login is required. It says nothing about pagination behavior, empty-list handling, or result caps, so the value added is modest.

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 short sentences with zero waste: the core action comes first, followed by the prerequisite. Nothing is repeated from the schema or annotations.

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?

With 0 required params, full schema coverage, an output schema, and read-only annotations, the description only needs to establish identity and the auth precondition, which it does. A note on pagination/limit interaction with large lists would make it complete, but no essential information is missing.

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 both enums (sort, status) are documented inline, so the schema carries the parameter burden. The description's mention of 'status, score and progress' refers to returned fields rather than adding meaning about the parameters; it neither clarifies nor misleads.

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?

States a specific verb and resource ('Get the authenticated user's own manga list') and scopes it to the current user, which separates it from get_manga / search_manga. It does not explicitly name the sibling alternative it competes with (e.g., get_my_anime_list, get_manga), but the 'own/authenticated' qualifier makes the distinction inferable.

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?

Usage is implied by 'the authenticated user's own manga list' and the login prerequisite, so an agent can tell this is for personal list data rather than catalog lookup. However, there is no explicit when-to-use/when-not guidance and no named alternative (e.g., 'use search_manga for public catalog data').

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

Deploy Server