Skip to main content
Glama

get_user_manga_list

Retrieve a user's manga list from AniList by providing their username or ID using the anilist-mcp server integration.

Instructions

Get a user's manga list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesUsername or user ID

Implementation Reference

  • Handler function that fetches the manga list for the given user using the AniList client and returns it as formatted JSON or an error response.
    async ({ user }) => {
      try {
        const list = await anilist.lists.manga(user);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(list, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Zod input schema 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:86-115 (registration)
    Full registration of the 'get_user_manga_list' tool via server.tool(), specifying name, description, input schema, execution hints, and the handler function.
    server.tool(
      "get_user_manga_list",
      "Get a user's manga list",
      {
        user: z.union([z.number(), z.string()]).describe("Username or user ID"),
      },
      {
        title: "Get User Manga List",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ user }) => {
        try {
          const list = await anilist.lists.manga(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?

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Get' implies a read operation, but it doesn't specify whether this requires authentication, returns paginated results, includes private lists, or has rate limits. For a user-specific data retrieval tool with zero annotation coverage, this leaves significant behavioral gaps.

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 states the core purpose without any fluff. It's appropriately sized for a simple retrieval tool and front-loads the essential information. Every word earns its place.

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 no annotations, no output schema, and a user-specific data retrieval operation, the description is incomplete. It doesn't address authentication requirements, return format, error conditions, or how it differs from similar tools. For a tool that likely returns structured user data, more context is needed for effective agent 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?

Schema description coverage is 100%, with the single parameter 'user' documented as 'Username or user ID'. The description adds no additional parameter information beyond what the schema provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even without param details in the description.

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 resource ('a user's manga list'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_user_anime_list' or 'get_manga', but the specificity of 'user's manga list' provides inherent distinction. This is clear but lacks explicit sibling comparison.

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_anime_list' or 'get_manga'. There's no mention of prerequisites, context, or exclusions. The agent must infer usage from the name alone, which is insufficient for optimal 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