Skip to main content
Glama
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Remove an entry from your AniList list

remove_list_entry
Destructive

Delete a specific entry from your AniList list by providing its list-entry ID. This action is permanent and cannot be undone.

Instructions

[Requires login] Delete an entry from the authenticated user's own AniList list by its list-entry ID (NOT the media id) — get it from get_user_list. This cannot be undone, and calling it again on an already-deleted id errors rather than silently succeeding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listEntryIdYesThe list ENTRY id to delete (not the media id).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • removedOutput schema / properties / result / properties / deleted / anyOf
      Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / result / properties / deleted / type
      Added value: +[
+  "boolean",
+  "null"
+]
  2. Changed2 schema fields changedv0.7.1
    • addedInput schema / properties / listEntryId / exclusiveMinimum
      Added value: +0
    • removedInput schema / properties / listEntryId / minimum
      Removed value: --2147483648
  3. Addedv0.3.0
  4. Removedv0.3.0
  5. Addedv0.2.0
  6. Removedv0.2.0
  7. First observedv0.1.5

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description explicitly states the operation cannot be undone and that repeating it on an already-deleted ID errors rather than silently succeeding. This is valuable behavioral context for an agent deciding whether to call the tool.

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 two sentences with no filler. It front-loads the required login, states the action, clarifies the ID type, and then covers irreversibility and error behavior—every sentence earns its place.

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

Completeness5/5

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

With one well-documented parameter, an output schema present, and annotations covering destructive and non-idempotent behavior, the description adds the remaining critical context: login requirement, ID source, and failure mode. Nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by pointing to get_user_list as the source for the list-entry ID and reiterating that it is not the media ID, which helps prevent a common misuse.

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 states a specific action ('Delete an entry') on a specific resource (the authenticated user's own AniList list) and clarifies the key distinction from media IDs. This clearly differentiates it from sibling tools like add_list_entry and update_list_entry.

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 description tells the agent where to obtain the required ID ('get it from get_user_list') and notes that login is required. It does not explicitly contrast with sibling delete tools, but the deletion purpose is unambiguous and the ID-source guidance is practical.

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