Skip to main content
Glama

delete_activity

Remove an activity post for the authorized user by specifying the AniList activity ID through the AniList MCP server.

Instructions

[Requires Login] Delete the current authorized user's activity post

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe AniList activity ID to delete

Implementation Reference

  • The handler function that executes the delete_activity tool: performs authentication check, deletes the AniList activity by ID, and returns a text response indicating success or failure, or an error.
    async ({ id }) => {
      try {
        const auth = requireAuth(config.anilistToken);
        if (!auth.isAuthorized) {
          return auth.errorResponse;
        }
    
        const result = await anilist.activity.delete(id);
        return {
          content: [
            {
              type: "text",
              text: result
                ? `Successfully deleted activity with ID ${id}.`
                : `Failed to delete activity with ID ${id}.`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Input schema requiring a numeric 'id' parameter and metadata hints indicating the tool is destructive but idempotent.
    {
      id: z.number().describe("The AniList activity ID to delete"),
    },
    {
      title: "Delete an AniList Activity",
      readOnlyHint: false,
      destructiveHint: true,
      idempotentHint: true,
      openWorldHint: true,
    },
  • The server.tool call that registers the delete_activity tool with its description, schema, metadata, and handler function within the registerActivityTools function.
    server.tool(
      "delete_activity",
      "[Requires Login] Delete the current authorized user's activity post",
      {
        id: z.number().describe("The AniList activity ID to delete"),
      },
      {
        title: "Delete an AniList Activity",
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: true,
        openWorldHint: true,
      },
      async ({ id }) => {
        try {
          const auth = requireAuth(config.anilistToken);
          if (!auth.isAuthorized) {
            return auth.errorResponse;
          }
    
          const result = await anilist.activity.delete(id);
          return {
            content: [
              {
                type: "text",
                text: result
                  ? `Successfully deleted activity with ID ${id}.`
                  : `Failed to delete activity with ID ${id}.`,
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the login requirement, which is useful, but fails to describe critical traits such as whether the deletion is permanent, if it affects associated data (e.g., comments), rate limits, or error conditions. For a destructive operation, this lack of detail is a notable shortfall.

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 extremely concise—just one sentence with the prerequisite in brackets—and front-loaded with the key action. There is no wasted verbiage, making it efficient and easy to parse.

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

Completeness2/5

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

Given the tool's complexity (a destructive delete operation) and the absence of both annotations and an output schema, the description is insufficient. It lacks details on behavioral outcomes, error handling, and return values, which are crucial for safe and effective use by an AI agent.

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?

The input schema has 100% description coverage, with the 'id' parameter documented as 'The AniList activity ID to delete'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without extra value.

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?

The description clearly states the action ('Delete') and the resource ('the current authorized user's activity post'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'delete_thread' or 'remove_list_entry', which prevents a perfect score.

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

Usage Guidelines2/5

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

The description includes '[Requires Login]' which provides some context about prerequisites, but it offers no guidance on when to use this tool versus alternatives like 'delete_thread' or 'remove_list_entry', nor does it specify conditions for deletion (e.g., ownership, timing). This leaves significant gaps in usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yuna0x0/anilist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server