Skip to main content
Glama

delete_thread

Remove an AniList thread by its ID using the anilist-mcp server. Requires login to delete unwanted or outdated discussions.

Instructions

[Requires Login] Delete a thread by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe AniList thread ID to delete

Implementation Reference

  • The async handler function for the 'delete_thread' tool. It requires authentication using requireAuth, calls anilist.thread.delete(id), handles the result, and returns a structured content response with success or error messages.
      async ({ id }) => {
        try {
          const auth = requireAuth(config.anilistToken);
          if (!auth.isAuthorized) {
            return auth.errorResponse;
          }
    
          const result = await anilist.thread.delete(id);
          return {
            content: [
              {
                type: "text",
                text: result
                  ? `Successfully deleted thread with ID ${id}.`
                  : `Failed to delete thread with ID ${id}.`,
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • Zod input schema for the 'delete_thread' tool, defining the required 'id' parameter as a number with description.
    {
      id: z.number().describe("The AniList thread ID to delete"),
    },
  • tools/thread.ts:13-51 (registration)
    Registration of the 'delete_thread' MCP tool using server.tool(), including name, description, input schema, tool hints (destructive, idempotent, etc.), and inline handler implementation.
    server.tool(
      "delete_thread",
      "[Requires Login] Delete a thread by its ID",
      {
        id: z.number().describe("The AniList thread ID to delete"),
      },
      {
        title: "Delete AniList Thread",
        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.thread.delete(id);
          return {
            content: [
              {
                type: "text",
                text: result
                  ? `Successfully deleted thread with ID ${id}.`
                  : `Failed to delete thread 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 full burden for behavioral disclosure. It mentions the login requirement (auth context) and implies destructive action through 'Delete', but fails to describe critical behaviors: whether deletion is permanent/reversible, what happens to associated comments/data, rate limits, permission requirements beyond login, or expected response format. For a destructive operation with zero annotation coverage, this leaves significant gaps.

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 at just 6 words, front-loading the critical login requirement and action. Every word earns its place: '[Requires Login]' sets context, 'Delete' specifies action, 'a thread' identifies resource, and 'by its ID' clarifies parameter usage. No wasted words or redundant information.

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?

For a destructive mutation tool with no annotations and no output schema, the description is incomplete. While concise, it lacks essential context: expected response format, error conditions, permanence of deletion, side effects on related data, and specific permission requirements. The '[Requires Login]' hint is helpful but insufficient for a tool that permanently removes data.

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% with the parameter 'id' fully documented as 'The AniList thread ID to delete'. The description adds no additional parameter semantics beyond what the schema provides, simply referencing 'by its ID'. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 resource ('a thread by its ID'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'delete_activity' or 'get_thread', but the specificity of 'thread' vs 'activity' provides some distinction. The description avoids tautology by not just restating the name.

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 provides minimal guidance with the '[Requires Login]' prefix, indicating a prerequisite condition. However, it offers no explicit guidance on when to use this tool versus alternatives like 'get_thread' (for viewing) or 'delete_activity' (for different resource types), nor does it specify any exclusion criteria or error conditions.

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