Skip to main content
Glama

add_list_entry

Add a media entry to your AniList profile with customizable details like status, score, progress, and notes. Requires user login for authorization.

Instructions

[Requires Login] Add an entry to the authorized user's list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe AniList ID of the media entry to add
optionsYesValues to save with the entry

Implementation Reference

  • The handler function for the add_list_entry tool. It authenticates using the AniList token, calls anilist.lists.addEntry with the provided id and options, and returns the JSON-stringified result or an error response.
      async ({ id, options }) => {
        try {
          const auth = requireAuth(config.anilistToken);
          if (!auth.isAuthorized) {
            return auth.errorResponse;
          }
    
          const result = await anilist.lists.addEntry(id, options);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • Zod schema defining the 'options' input for the add_list_entry tool, including fields for status, progress, scores, dates, and more for updating/adding list entries.
    export const UpdateEntryOptionsSchema = z
      .object({
        id: z.number().describe("The ID of the list entry"),
        mediaId: z.number().describe("The ID of the media to add"),
        status: EntryStatusSchema.describe("The status of the media on the list"),
        score: z.number().describe("The score given to the media"),
        scoreRaw: z.number().describe("The raw score in 100 point format"),
        progress: z.number().describe("The amount of episodes/chapters consumed"),
        progressVolumes: z
          .number()
          .describe("The amount of volumes read (manga only)"),
        repeat: z.number().describe("Amount of times the media has been repeated"),
        priority: z.number().describe("Priority level of the media"),
        private: z.boolean().describe("Whether the entry should be private"),
        notes: z.string().describe("Text notes about the media"),
        hiddenFromStatusLists: z
          .boolean()
          .describe("Whether the entry should be hidden from non-custom lists"),
        customLists: z
          .array(z.string())
          .describe("Array of custom list names for the media"),
        advancedScores: z
          .array(z.number())
          .describe("Advanced scores as an object"),
        startedAt: z
          .object({
            year: z.number(),
            month: z.number(),
            day: z.number(),
          })
          .describe("When the user started the media"),
        completedAt: z
          .object({
            year: z.number(),
            month: z.number(),
            day: z.number(),
          })
          .describe("When the user completed the media"),
      })
      .describe("Values to save with the entry");
  • tools/lists.ts:15-51 (registration)
    Registers the add_list_entry tool on the MCP server within the registerListsTools function, specifying name, description, input schema (id and options), tool properties, and handler.
      "add_list_entry",
      "[Requires Login] Add an entry to the authorized user's list",
      {
        id: z.number().describe("The AniList ID of the media entry to add"),
        options: UpdateEntryOptionsSchema,
      },
      {
        title: "Add List Entry",
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: true,
        openWorldHint: true,
      },
      async ({ id, options }) => {
        try {
          const auth = requireAuth(config.anilistToken);
          if (!auth.isAuthorized) {
            return auth.errorResponse;
          }
    
          const result = await anilist.lists.addEntry(id, options);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • tools/index.ts:33-33 (registration)
    Top-level call to registerListsTools in registerAllTools, which includes the add_list_entry tool registration.
    registerListsTools(server, anilist, config);
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 authentication requirement ('[Requires Login]') which is helpful, but doesn't describe what happens when adding an entry - whether it creates a new record, what the response looks like, potential side effects, or error conditions. For a mutation tool with complex parameters, this is insufficient.

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 a bracketed prerequisite. It's front-loaded with the authentication requirement and states the core purpose efficiently. Every word serves a purpose with no wasted text.

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 mutation tool with 2 complex parameters (including a nested object with 16 required properties), no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, how to interpret results, or provide context about the list system. The authentication note is helpful but insufficient for the tool's complexity.

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%, so the schema fully documents both parameters and their nested properties. The description doesn't add any parameter-specific information beyond what's in the schema, but since the schema is comprehensive, the baseline score of 3 is appropriate.

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 ('Add an entry') and target ('to the authorized user's list'), which is specific and actionable. However, it doesn't distinguish this tool from its sibling 'update_list_entry' or 'remove_list_entry', which handle similar list operations but with different verbs.

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 basic authentication context, but offers no guidance on when to use this tool versus alternatives like 'update_list_entry' or 'remove_list_entry'. There's no mention of prerequisites beyond login or comparison with sibling tools.

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