MyAnimeList MCP Server

by MorpKnight

Overview Schema Source Related Servers Discussions Admin

Python

Local

update_myanimelist

Update your MyAnimeList anime entries with scores, status, comments, and rewatch details using the anime's ID.

Instructions

Update fields on an anime 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": {
      "anime_id": "<anime_id>"
    },
    "name": "update_myanimelist"
  }
}

Input Schema

Name	Required	Description
`tags`	No
`score`	No	Score from 0 to 10
`status`	No
`anime_id`	Yes	MyAnimeList anime ID
`comments`	No
`priority`	No
`is_rewatching`	No
`rewatch_value`	No
`num_times_rewatched`	No
`num_watched_episodes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 1, 2026

TDQS

B3.2/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 only mentions 'authenticated user's' (implying auth), but does not disclose partial-update behavior, whether new entries can be created, error handling, or idempotency. For a mutation tool, this is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single, front-loaded sentence with no redundant wording. While it is terse and could include more detail, it is appropriately concise for the minimal information it conveys.

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?

With 10 parameters (most undocumented), no output schema, and no annotations, the one-sentence description is inadequate for an agent to safely invoke the tool. It lacks behavior details, parameter meanings, and update semantics, making it incomplete for the tool's complexity.

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 20% (score and anime_id have descriptions). The description refers to 'fields' generically without enumerating the updatable parameters or explaining enum values, numeric ranges, or semantics like is_rewatching vs rewatch_value. It fails to compensate for the sparse schema.

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 verb ('Update'), the resource ('anime in the authenticated user's MAL list'), and scope. It distinguishes itself from siblings like delete_myanimelist_item and update_mymangalist, leaving no ambiguity about what this tool does.

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 modifying existing list entries via the authenticated user's context, but it does not explicitly state when to use it versus alternatives, nor does it mention prerequisites like 'the anime must already be in the list.' No exclusions or alternative tool references are given.

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

Deploy Server