Skip to main content
Glama
Sign In
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Delete a comment on a forum thread

delete_thread_comment
Destructive

Delete a thread comment owned by the authenticated AniList user by its ID. Use it to remove comments permanently; deleted IDs return not found.

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 as not found rather than silently succeeding.

Input Schema

NameRequiredDescriptionDefault
idYesAniList comment ID to delete.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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"
+]
  3. Changed2 schema fields changedv0.7.1
    • addedInput schema / properties / id / exclusiveMinimum
      Added value: +0
    • removedInput schema / properties / id / minimum
      Removed value: --2147483648
  4. Addedv0.2.0
  5. Removedv0.2.0
  6. First observedv0.1.5

TDQS

A4.7/5.0
Behavior5/5

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

Adds real information beyond the annotations: the auth requirement, the ownership precondition, and the precise repeat-call behavior (a second call errors as not found rather than silently succeeding), which sharpens the generic idempotentHint=false into actionable semantics. Combined with confirming irreversibility, this is behavior an agent cannot get from the structured fields alone.

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?

Three short clauses, front-loaded with the auth gate and the action, then the id source, then the destructive and error semantics. No filler sentences and nothing that merely restates the schema.

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 tool with a full annotation set and an output schema, everything an agent needs before invoking — login requirement, ownership, id provenance, irreversibility, repeat-call result — is present. Return values are left to the output schema appropriately.

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% for the single id parameter, so baseline is 3; the description earns above that by explaining where valid ids originate (get_thread_comments, post_thread_comment) and tying the value to the caller's own comments. It adds provenance rather than type detail, which the schema already covers.

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 a specific verb and resource ("Delete a comment") plus two scoping constraints: it must be owned by the authenticated user and identified by ID. That scope distinguishes it cleanly from the sibling delete_thread, which deletes a whole thread rather than a comment.

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?

Gives the precondition ([Requires login]), the ownership restriction, and explicitly names where the id comes from (get_thread_comments or the id returned by post_thread_comment). It stops short of saying when not to use it (e.g. use delete_thread for whole threads), so it is clear but not fully routing.

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