Skip to main content
Glama
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Delete a comment on a forum thread

delete_thread_comment
Destructive

Delete a thread comment you own on AniList by its ID. This permanently removes the comment and cannot be undone.

Instructions

[Requires login] Delete a comment the authenticated user owns, by its ID (from get_thread_comments or the id returned by post_thread_comment). This cannot be undone, and calling it again on an already-deleted id errors rather than silently succeeding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAniList comment ID to delete.

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 / id / exclusiveMinimum
      Added value: +0
    • removedInput schema / properties / id / minimum
      Removed value: --2147483648
  3. Addedv0.2.0
  4. Removedv0.2.0
  5. First observedv0.1.5

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate destructive and non-idempotent behavior, but the description adds meaningful context: login is required, only the owner's comment can be deleted, deletion cannot be undone, and repeating the call on an already-deleted ID errors instead of silently succeeding. This goes well beyond the annotations.

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?

Two dense sentences front-load the critical login requirement, then cover ownership, ID source, irreversibility, and repeated-call behavior with no filler. Every clause 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?

For a single-parameter destructive operation with an output schema and rich annotations, the description covers prerequisites, ownership rules, ID provenance, and idempotency semantics. Nothing needed for correct invocation 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?

The schema fully documents the 'id' parameter with a clear description and range. The tool description adds valuable provenance information, explaining exactly where the ID comes from, which supplements rather than merely repeats the 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?

States the exact operation (delete), the resource (a forum thread comment), and the ownership constraint (the authenticated user's own comment). This clearly distinguishes it from sibling tools like delete_thread and delete_activity.

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 explicitly says the comment must be owned by the authenticated user and tells the caller where to get the ID (from get_thread_comments or post_thread_comment). It does not explicitly contrast with delete_thread or delete_activity, but the context makes the applicable case clear.

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