Skip to main content
Glama

favourite_anime

Mark or unmark an anime as a favorite using its AniList ID. Requires login to manage preferences directly through the AniList MCP server.

Instructions

[Requires Login] Favourite or unfavourite an anime by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe AniList ID of the anime to favourite/unfavourite

Implementation Reference

  • tools/media.ts:68-107 (registration)
    Registration of the 'favourite_anime' MCP tool, including description, input schema, metadata hints, and inline handler function that performs auth check and calls the external anilist.media.favouriteAnime(id).
      "favourite_anime",
      "[Requires Login] Favourite or unfavourite an anime by its ID",
      {
        id: z
          .number()
          .describe("The AniList ID of the anime to favourite/unfavourite"),
      },
      {
        title: "Favourite/Unfavourite Anime",
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: false,
        openWorldHint: true,
      },
      async ({ id }) => {
        try {
          const auth = requireAuth(config.anilistToken);
          if (!auth.isAuthorized) {
            return auth.errorResponse;
          }
    
          const result = await anilist.media.favouriteAnime(id);
          return {
            content: [
              {
                type: "text",
                text: result
                  ? `Successfully added anime with ID ${id} to favourites.`
                  : `Anime with ID ${id} was removed from favourites or operation failed.`,
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • The core handler logic for the 'favourite_anime' tool: checks authentication using requireAuth, toggles the anime favorite status via anilist.media.favouriteAnime(id), and returns success/error message.
    async ({ id }) => {
      try {
        const auth = requireAuth(config.anilistToken);
        if (!auth.isAuthorized) {
          return auth.errorResponse;
        }
    
        const result = await anilist.media.favouriteAnime(id);
        return {
          content: [
            {
              type: "text",
              text: result
                ? `Successfully added anime with ID ${id} to favourites.`
                : `Anime with ID ${id} was removed from favourites or operation failed.`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Input schema using Zod: requires 'id' as a number (AniList anime ID).
    {
      id: z
        .number()
        .describe("The AniList ID of the anime to favourite/unfavourite"),
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the login requirement, which is useful context, but fails to disclose key behavioral traits such as whether this is a toggle (favourite/unfavourite), the effect on existing data, rate limits, or error conditions. For a mutation tool with zero annotation coverage, this is a significant gap.

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. It is front-loaded with the key requirement and action, with zero wasted words, making it highly 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 incomplete. It covers the login requirement but misses critical details like behavioral outcomes (e.g., toggle behavior), error handling, or return values, leaving the agent with insufficient context for reliable use.

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 ID of the anime to favourite/unfavourite'. The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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 ('favourite or unfavourite') and the resource ('an anime by its ID'), making the purpose specific and understandable. It distinguishes from siblings like 'favourite_character' or 'favourite_manga' by specifying anime, though it doesn't explicitly contrast with them in the text.

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 description includes '[Requires Login]' as a prerequisite, providing some context for when to use it. However, it lacks explicit guidance on when to choose this tool over alternatives (e.g., how it differs from other favourite_* tools) or any exclusions, leaving usage somewhat implied.

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