Skip to main content
Glama

remove_list_entry

Remove an entry from your AniList account by specifying its list ID. Use this tool to manage your anime or manga list efficiently, requiring a valid login for access.

Instructions

[Requires Login] Remove an entry from the authorized user's list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe AniList list ID of the entry to remove

Implementation Reference

  • tools/lists.ts:118-156 (registration)
    Registration of the 'remove_list_entry' tool using server.tool(). Includes inline input schema (id: number), metadata, and the handler function that authenticates, calls anilist.lists.removeEntry(id), and returns success/error response.
    server.tool(
      "remove_list_entry",
      "[Requires Login] Remove an entry from the authorized user's list",
      {
        id: z.number().describe("The AniList list ID of the entry to remove"),
      },
      {
        title: "Remove List Entry",
        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.lists.removeEntry(id);
          return {
            content: [
              {
                type: "text",
                text: result
                  ? `Successfully removed list entry with ID ${id}.`
                  : `Failed to remove list entry with ID ${id}.`,
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • The inline handler function for 'remove_list_entry' tool. Performs authentication check, removes the list entry using the AniList client, and formats the response.
    async ({ id }) => {
      try {
        const auth = requireAuth(config.anilistToken);
        if (!auth.isAuthorized) {
          return auth.errorResponse;
        }
    
        const result = await anilist.lists.removeEntry(id);
        return {
          content: [
            {
              type: "text",
              text: result
                ? `Successfully removed list entry with ID ${id}.`
                : `Failed to remove list entry with ID ${id}.`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Input schema for the 'remove_list_entry' tool, requiring a numeric 'id' parameter representing the AniList list entry ID.
    {
      id: z.number().describe("The AniList list ID of the entry to remove"),
    },
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, which is useful, but fails to describe critical traits like whether the removal is permanent, reversible, or has side effects (e.g., affecting user stats). For a mutation tool, this leaves significant gaps in understanding its behavior.

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 with only one sentence, front-loading the login requirement and action. There is no wasted text, 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 this is a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on what 'remove' entails (e.g., deletion vs. archiving), error conditions, or return values, leaving the agent with incomplete context for safe invocation.

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 schema description coverage is 100%, with the 'id' parameter clearly documented in the schema. The description adds no additional parameter semantics beyond implying the 'id' refers to a list entry, which is already covered. This meets the baseline for high schema coverage.

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 ('Remove') and target ('an entry from the authorized user's list'), making the purpose understandable. However, it doesn't distinguish this tool from similar siblings like 'delete_activity' or 'delete_thread', which also perform removal operations but on different resources.

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 '[Requires Login]', indicating a prerequisite but not when to use this tool versus alternatives. No explicit comparisons to siblings like 'update_list_entry' or 'add_list_entry' are made, leaving usage context vague.

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