Skip to main content
Glama

search_user

Find users on AniList by entering a search term, specifying results per page, and navigating through paginated results using the MCP server.

Instructions

Search for users on AniList

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoResults per page (max 25)
pageNoPage number for results
termYesSearch term for finding users

Implementation Reference

  • Handler function for the 'search_user' tool that performs a user search on AniList via anilist.searchEntry.user and returns JSON results or error.
    async ({ term, page, amount }) => {
      try {
        const results = await anilist.searchEntry.user(term, page, amount);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(results, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Zod input schema defining parameters for the 'search_user' tool: term (required string), page and amount (optional numbers with defaults).
    {
      term: z.string().describe("Search term for finding users"),
      page: z
        .number()
        .optional()
        .default(1)
        .describe("Page number for results"),
      amount: z
        .number()
        .optional()
        .default(5)
        .describe("Results per page (max 25)"),
    },
  • Registration of the 'search_user' tool on the MCP server, including name, description, input schema, metadata, and handler.
    server.tool(
      "search_user",
      "Search for users on AniList",
      {
        term: z.string().describe("Search term for finding users"),
        page: z
          .number()
          .optional()
          .default(1)
          .describe("Page number for results"),
        amount: z
          .number()
          .optional()
          .default(5)
          .describe("Results per page (max 25)"),
      },
      {
        title: "AniList User Search",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ term, page, amount }) => {
        try {
          const results = await anilist.searchEntry.user(term, page, amount);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(results, 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 full burden for behavioral disclosure but only states the basic action. It doesn't describe what the search returns (user objects, IDs, profiles), whether it's paginated (implied by parameters but not stated), authentication requirements, rate limits, or search algorithm characteristics. This leaves significant behavioral gaps for a search operation.

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 unnecessary words. It's appropriately sized for a search tool and front-loads the essential information. Every word earns its place in this concise formulation.

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 search tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what constitutes a 'user' in this context, what fields are searchable, what the return format looks like, or how results are ordered. The agent would need to guess about the search behavior and result structure based solely on parameter descriptions.

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 already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it mentions 'search term' which aligns with the 'term' parameter but provides no extra context about search syntax, matching behavior, or result ordering.

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 ('Search for users') and resource ('on AniList'), making the purpose immediately understandable. However, it doesn't differentiate this user search from sibling search tools like search_anime or search_character, which follow the same pattern but target different resources.

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. There's no mention of when search_user is appropriate versus get_user_profile or get_full_user_info, nor any context about search scope, limitations, or prerequisites for using this search functionality.

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