Skip to main content
Glama

favourite_staff

Use the tool to favourite or unfavourite a staff member on AniList by entering their unique ID, enabling easy management of preferred profiles.

Instructions

[Requires Login] Favourite or unfavourite a staff member by their ID

Input Schema

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

Implementation Reference

  • The handler function for the 'favourite_staff' tool. It authenticates the user, toggles the staff member's favourite status using anilist.people.favouriteStaff(id), and returns an appropriate response message.
    async ({ id }) => {
      try {
        const auth = requireAuth(config.anilistToken);
        if (!auth.isAuthorized) {
          return auth.errorResponse;
        }
    
        const result = await anilist.people.favouriteStaff(id);
        return {
          content: [
            {
              type: "text",
              text: result
                ? `Successfully added staff member with ID ${id} to favourites.`
                : `Staff member 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, defining the 'id' parameter as a required number (AniList staff ID).
    {
      id: z
        .number()
        .describe(
          "The AniList ID of the staff member to favourite/unfavourite",
        ),
    },
  • tools/people.ts:89-132 (registration)
    Full registration of the 'favourite_staff' tool using server.tool(), including name, description, input schema, metadata hints, and inline handler.
    // anilist.people.favouriteStaff()
    server.tool(
      "favourite_staff",
      "[Requires Login] Favourite or unfavourite a staff member by their ID",
      {
        id: z
          .number()
          .describe(
            "The AniList ID of the staff member to favourite/unfavourite",
          ),
      },
      {
        title: "Favourite/Unfavourite Staff Member",
        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.people.favouriteStaff(id);
          return {
            content: [
              {
                type: "text",
                text: result
                  ? `Successfully added staff member with ID ${id} to favourites.`
                  : `Staff member with ID ${id} was removed from favourites or operation failed.`,
              },
            ],
          };
        } 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 context. However, it doesn't describe other important traits such as whether this is a toggle operation (favourite/unfavourite), what happens on success/failure, rate limits, or any side effects. For a mutation tool with zero annotation coverage, 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 and front-loaded, consisting of just two parts: the prerequisite in brackets and the core action. Every element earns its place by providing essential information without any wasted words or redundant phrasing, making it highly efficient.

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 as a mutation operation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., toggle nature, response format, error handling) and doesn't compensate for the absence of structured data. While concise, it doesn't provide enough context 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 clearly documented as 'The AniList ID of the staff member to favourite/unfavourite'. The description doesn't add any additional meaning beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 target resource ('a staff member by their ID'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from similar sibling tools like 'favourite_anime', 'favourite_character', 'favourite_manga', and 'favourite_studio', which all perform analogous operations on different resource types.

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 a prerequisite ('[Requires Login]'), which provides some context for when to use this tool. However, it doesn't offer explicit guidance on when to choose this tool over alternatives (e.g., other 'favourite_' tools for different resource types) or any exclusions. The usage is implied but not fully elaborated.

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