Skip to main content
Glama
Sign In
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Delete a forum thread

delete_thread
Destructive

Delete a forum thread by ID that you own as the authenticated user. Requires login; irreversible and errors if already deleted.

Instructions

[Requires login] Delete a forum thread the authenticated user owns, by its ID (from search_thread, get_thread, or the id returned by post_thread). 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 thread 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.3.0
  5. Removedv0.2.0
  6. First observedv0.1.5

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructive/non-idempotent/open-world, so the bar is lower, and the description still contributes real context: login and ownership requirements and the second-call not-found behavior. 'Cannot be undone' largely restates destructiveHint, so the value-add is good but not exceptional.

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?

A single dense sentence with the auth requirement front-loaded, followed by the irreversible/error semantics. No filler and nothing deferred to the end that belongs at the front.

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 one-parameter destructive mutation with an output schema and full annotation coverage, everything an agent needs is present: auth gate, ownership constraint, ID provenance, irreversibility, and repeat-call behavior.

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% and there is only one parameter, so semantics are already carried by the schema; the description adds genuine value by telling the agent where a valid ID comes from (search_thread, get_thread, post_thread).

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 (delete) and resource (a forum thread the authenticated user owns, by ID), which cleanly separates it from delete_thread_comment, delete_activity, and the read-only thread tools. The parenthetical naming search_thread/get_thread/post_thread as ID sources removes ambiguity about the input's origin.

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 clear preconditions: login required and ownership required, plus a warning that repeating the call errors as not found instead of succeeding silently. It never explicitly steers to siblings like delete_thread_comment, so it stops short of a full when/when-not/alternatives statement.

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