Skip to main content
Glama

search_studio

Find studios matching a specific search term using an AniList-powered tool. Enter a query term, page number, and results per page to retrieve curated studio data efficiently.

Instructions

Search for studios based on a query term

Input Schema

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

Implementation Reference

  • Handler function that executes the search_studio tool by calling anilist.searchEntry.studio with the provided term, page, and amount parameters, returns formatted JSON results or an error message.
    async ({ term, page, amount }) => {
      try {
        const results = await anilist.searchEntry.studio(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,
        };
      }
    },
  • Input schema using Zod validators for the search_studio tool parameters: term (required string), page (optional number, default 1), amount (optional number, default 5).
    {
      term: z.string().describe("Search term for finding studios"),
      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_studio tool using server.tool(), specifying name, description, input schema, metadata, and handler function.
    server.tool(
      "search_studio",
      "Search for studios based on a query term",
      {
        term: z.string().describe("Search term for finding studios"),
        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 Studio Search",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ term, page, amount }) => {
        try {
          const results = await anilist.searchEntry.studio(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 but only states the basic action. It doesn't disclose behavioral traits like pagination behavior (implied by parameters but not described), rate limits, authentication needs, or what the search returns (e.g., partial vs. full results). This is a significant gap for a tool with parameters and no output schema.

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 with zero waste. It's front-loaded and appropriately sized for a simple search tool, 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 no annotations, no output schema, and 3 parameters, the description is incomplete. It doesn't explain what the search returns, how results are structured, or any behavioral context like error handling. For a search tool with pagination parameters, this leaves the agent with insufficient information to use it 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?

Schema description coverage is 100%, so the schema fully documents parameters like 'term', 'amount', and 'page'. The description adds no additional meaning beyond implying a search term is used, which is already covered. Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('Search') and resource ('studios'), specifying it's based on a query term. It distinguishes from non-search siblings but doesn't explicitly differentiate from other search tools like search_anime or search_character, which have similar patterns.

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?

No guidance on when to use this tool versus alternatives is provided. It doesn't mention when to prefer this over get_studio (which might fetch a specific studio) or how it differs from other search tools in the sibling list, leaving usage context implied at best.

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