Skip to main content
Glama
Sign In
MyAnimeList MCP Server

MyAnimeList MCP Server

by MorpKnight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_myanimelist_item

Delete an anime from your MyAnimeList list using its anime ID. Simplifies updating your personal anime collection.

Instructions

Delete one anime from 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": "delete_myanimelist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
anime_idYesMyAnimeList anime ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/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 of behavioral disclosure. It says 'Delete' but does not mention that the action is permanent, what happens if the anime isn't on the list, or any specific authentication requirements beyond the phrase 'authenticated user's.' For a destructive operation, this is insufficient.

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, tightly written sentence with no filler or redundancy. It earns its place by stating the exact action and target in the fewest words possible.

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

Completeness3/5

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

For a one-parameter delete tool with no output schema, the description covers the core action and implies authentication, but it omits side effects and error cases. It is minimally adequate given the low complexity.

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 coverage is 100% and the description adds no additional meaning beyond what the schema provides for anime_id. The baseline of 3 applies because the schema fully documents the parameter.

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 uses the specific verb 'Delete' with the resource 'anime' and scope 'authenticated user's MAL list,' clearly distinguishing it from sibling get/update tools. It is immediately obvious 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 Guidelines4/5

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

The context is clear: use this when you want to remove an anime from the authenticated user's MyAnimeList. It doesn't explicitly exclude alternatives, but the sibling names (e.g., delete_mymangalist_item, update_myanimelist) make the intended use unambiguous.

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

Deploy Server

Other Tools