Skip to main content
Glama
Sign In
MyAnimeList MCP Server

MyAnimeList MCP Server

by MorpKnight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_mymangalist_item

Delete a manga from your MyAnimeList by providing its ID. Removes the entry from your list.

Instructions

Delete one manga 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": {
      "manga_id": "<manga_id>"
    },
    "name": "delete_mymangalist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
manga_idYesMyAnimeList manga ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, so the description must carry the full burden. It states the delete action but does not disclose irreversibility, authentication prerequisites, error behavior, or side effects. This is a significant gap for a destructive operation.

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 with no wasted words or redundant details. It front-loads the essential information and is easily scannable.

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 simple one-parameter delete tool, the description is minimally sufficient but lacks context about success/error responses, prerequisites, or idempotency. The absence of an output schema and the sparse behavioral detail prevent it from being fully complete.

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?

The schema provides 100% coverage with a description for manga_id ('MyAnimeList manga ID'). The tool description adds no additional parameter meaning, so based on the high schema coverage baseline, a score of 3 is appropriate.

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?

Description clearly states 'Delete one manga from the authenticated user's MAL list.' It uses a specific verb ('delete') and resource ('manga from authenticated user's MAL list'), and the mention of 'manga' distinguishes it from the sibling tool delete_myanimelist_item.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. It does not mention conditions, exclusions, or alternatives. The name and description imply the purpose, but no explicit usages or comparisons are provided.

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