Skip to main content
Glama
Sign In
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Delete an activity post

delete_activity
Destructive

Delete an AniList activity post owned by the authenticated user by ID; requires login and permanently removes the post, so verify the ID before calling because deletion cannot be undone.

Instructions

[Requires login] Delete an activity post the authenticated user owns. 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 activity ID to delete — from get_user_activity, get_user_recent_activity, search_activity, or the id returned by a previous post_text_activity/post_message_activity call.

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. Changed3 schema fields changedv0.7.1
    • changedInput schema / properties / id / description
      Previous value: -"AniList activity ID to delete — from get_user_activity, search_activity, or the id returned by a previous post_text_activity/post_message_activity call."New value: +"AniList activity ID to delete — from get_user_activity, get_user_recent_activity, search_activity, or the id returned by a previous post_text_activity/post_message_activity call."
    • 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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=false and openWorld=true, yet the description adds real value: the login requirement and the concrete failure mode (repeat calls on a deleted id error as not found rather than silently succeeding). The remaining gap is that it doesn't say whether attached replies/comments are also removed.

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 tight sentences: auth requirement and scope first, then irreversibility and repeat-call behavior. No filler.

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

Completeness4/5

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

Output schema and rich annotations carry the safety profile, so the description only needs auth, irreversibility and error semantics — all present. It could be more complete by noting cascade effects on child comments for a destructive delete.

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?

Schema description coverage is 100% and the id field already documents its provenance (get_user_activity, search_activity, prior post_text_activity calls). The description adds nothing about the parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Delete) and resource (activity post) plus the ownership constraint, which lets an agent separate it from delete_thread or remove_list_entry. It does not explicitly name an alternative, but the resource is unambiguous.

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

Usage Guidelines3/5

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

The '[Requires login]' tag gives an actionable prerequisite, and 'the authenticated user owns' implies you should only target your own posts. There is no explicit when-to-use vs a sibling (e.g. delete_thread_comment for comment-level removal), so routing is left to inference.

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