Skip to main content
Glama

search_manga

Search for manga using query terms and filters like genre, tag, format, or publication date. Access results sorted by criteria such as popularity, score, or release date.

Instructions

Search for manga with query term and filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoResults per page (max 25)
filterNoFilter object for searching manga. You MUST NOT include "{ "type": "MANGA" }" in the filter object. As it is already included in the API call. When no sorting method or any filter is specified, you SHOULD use the site default: "{ "sort": ["SEARCH_MATCH"] }". Otherwise, request is likely to fail or return no results.
pageNoPage number for results
termNoQuery term for finding manga (leave it as undefined when no query term specified.) Query term is used for searching with specific word or title in mind. You SHOULD not include things that can be found in the filter object, such as genre or tag. Those things should be included in the filter object instead. To check whether a user requested term should be considered as a query term or a filter term. It is recommended to use tools like 'get_genres' and 'get_media_tags' first.

Implementation Reference

  • Handler function that executes the search_manga tool by calling anilist.searchEntry.manga with provided term, filter, page, and amount parameters, returning JSON-stringified results or an error message.
    async ({ term, filter, page, amount }) => {
      try {
        const results = await anilist.searchEntry.manga(
          term,
          filter,
          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 search_manga: optional term (string), filter (MediaFilterTypesSchema), page (number, default 1), amount (number, default 5). Includes detailed descriptions.
        {
          term: z
            .string()
            .optional()
            .describe(
              `Query term for finding manga (leave it as undefined when no query term specified.)
    Query term is used for searching with specific word or title in mind.
    
    You SHOULD not include things that can be found in the filter object, such as genre or tag.
    Those things should be included in the filter object instead.
    
    To check whether a user requested term should be considered as a query term or a filter term.
    It is recommended to use tools like 'get_genres' and 'get_media_tags' first.`,
            ),
          filter: MediaFilterTypesSchema.optional().describe(
            `Filter object for searching manga.
    You MUST NOT include "{ "type": "MANGA" }" in the filter object. As it is already included in the API call.
    When no sorting method or any filter is specified, you SHOULD use the site default: "{ "sort": ["SEARCH_MATCH"] }".
    Otherwise, request is likely to fail or return no results.`,
          ),
          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_manga tool via server.tool(), specifying name, description, input schema, hints (title, readOnlyHint, openWorldHint), and handler function within the registerSearchTools function.
      server.tool(
        "search_manga",
        "Search for manga with query term and filters",
        {
          term: z
            .string()
            .optional()
            .describe(
              `Query term for finding manga (leave it as undefined when no query term specified.)
    Query term is used for searching with specific word or title in mind.
    
    You SHOULD not include things that can be found in the filter object, such as genre or tag.
    Those things should be included in the filter object instead.
    
    To check whether a user requested term should be considered as a query term or a filter term.
    It is recommended to use tools like 'get_genres' and 'get_media_tags' first.`,
            ),
          filter: MediaFilterTypesSchema.optional().describe(
            `Filter object for searching manga.
    You MUST NOT include "{ "type": "MANGA" }" in the filter object. As it is already included in the API call.
    When no sorting method or any filter is specified, you SHOULD use the site default: "{ "sort": ["SEARCH_MATCH"] }".
    Otherwise, request is likely to fail or return no results.`,
          ),
          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 Manga Search",
          readOnlyHint: true,
          openWorldHint: true,
        },
        async ({ term, filter, page, amount }) => {
          try {
            const results = await anilist.searchEntry.manga(
              term,
              filter,
              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 mention whether this is a read-only operation, potential rate limits, authentication requirements, pagination behavior, or error conditions. For a search tool with complex parameters, this is inadequate.

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 with just 7 words, front-loading the core purpose without any wasted language. Every word serves a clear function in communicating the tool's basic intent.

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 complex search tool with 4 parameters (including a nested filter object with 60+ properties), no annotations, and no output schema, the description is insufficient. It doesn't explain what results look like, how pagination works, error handling, or the relationship between term and filter parameters. The schema does heavy lifting, but the description should provide more operational context.

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 parameters thoroughly. The description adds minimal value by mentioning 'query term and filters' but doesn't provide additional context beyond what's in the schema. This meets the baseline for high schema coverage.

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 tool's purpose as 'Search for manga with query term and filters', which is a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'search_anime' or 'search_character' beyond the manga focus, missing explicit sibling distinction.

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_manga' or 'search_anime'. It lacks any context about prerequisites, typical use cases, or comparison with sibling tools, offering minimal usage direction.

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