Skip to main content
Glama

get_user_anime_list

Retrieve a user's anime list using their username or ID. Integrate with the AniList MCP server to access and manage anime-related data efficiently.

Instructions

Get a user's anime list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesUsername or user ID

Implementation Reference

  • The handler function for the 'get_user_anime_list' tool. It fetches the anime list for the given user (ID or username) using the AniList client, returns the JSON-stringified list as text content, or an error message if failed.
    async ({ user }) => {
      try {
        const list = await anilist.lists.anime(user);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(list, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Input schema for the tool, defining the 'user' parameter as either a number (user ID) or string (username).
    {
      user: z.union([z.number(), z.string()]).describe("Username or user ID"),
    },
  • tools/lists.ts:54-83 (registration)
    Registration of the 'get_user_anime_list' tool on the MCP server, specifying name, description, input schema, metadata hints, and the handler function.
    server.tool(
      "get_user_anime_list",
      "Get a user's anime list",
      {
        user: z.union([z.number(), z.string()]).describe("Username or user ID"),
      },
      {
        title: "Get User Anime List",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ user }) => {
        try {
          const list = await anilist.lists.anime(user);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(list, null, 2),
              },
            ],
          };
        } 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 states a read operation ('Get'), which implies safety, but fails to mention critical details like authentication requirements, rate limits, pagination, or the format of the returned anime list. This leaves significant gaps in understanding how the tool behaves.

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 a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and perfectly sized for its minimal content, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like authentication, rate limits, or response format, which are crucial for a tool that retrieves user-specific data. This leaves the agent with insufficient information to use the tool effectively.

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, clearly documenting the 'user' parameter as a username or user ID. The description adds no additional semantic context beyond what the schema provides, such as examples or constraints, so it meets the baseline for adequate but unenhanced parameter documentation.

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 verb 'Get' and the resource 'a user's anime list', which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'get_user_manga_list' or 'get_user_activity', which would require explicit distinction for a perfect score.

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 no guidance on when to use this tool versus alternatives like 'get_user_manga_list' or 'get_user_profile'. It lacks any context about prerequisites, such as whether the user must be public or authenticated, which is essential for effective tool selection.

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