MyAnimeList MCP Server

by MorpKnight

Overview Schema Source Related Servers Discussions Admin

Python

Local

update_mymangalist

Update manga details in your MyAnimeList list, including status, score, progress, and comments.

Instructions

Update fields on a manga in the authenticated user's MAL list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "manga_id": "<manga_id>"
    },
    "name": "update_mymangalist"
  }
}

Input Schema

Name	Required	Description
`tags`	No
`score`	No	Score from 0 to 10
`status`	No
`comments`	No
`manga_id`	Yes	MyAnimeList manga ID
`priority`	No
`is_rereading`	No
`reread_value`	No
`num_times_reread`	No
`num_volumes_read`	No
`num_chapters_read`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 1, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that the operation targets the authenticated user's MAL list, implying authentication is required, but it does not mention reversibility, error behavior, or that existing values may be overwritten.

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 a single concise sentence that front-loads the action and the target, with no redundant words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 11 parameters and no output schema, yet the description provides no information about return values, error conditions, or which fields are commonly updated together. This is insufficient for an AI agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 18%, and the description adds no parameter-specific information. It merely says 'Update fields' without elaborating on which fields or any parameter semantics beyond what the schema already provides.

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?

The description clearly states the tool's function with a specific verb ('Update') and resource ('manga in the authenticated user's MAL list'), and the name distinguishes it from sibling tools like update_myanimelist.

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?

The description implies usage for updating the user's manga list but provides no explicit guidance on when to use this tool versus alternatives such as update_myanimelist for anime or delete_mymangalist_item for deletions.

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

Deploy Server