Skip to main content
Glama

get_studio

Retrieve detailed information about a studio using its AniList ID or name, enabling quick access to essential data via the AniList MCP server.

Instructions

Get information about a studio by its AniList ID or name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
studioYesThe studio ID or name

Implementation Reference

  • tools/misc.ts:147-177 (registration)
    Full registration of the 'get_studio' MCP tool, including name, description, Zod input schema for 'studio' parameter (ID or name), tool hints, and inline handler function that uses anilist.studio() to fetch data and returns formatted JSON or error.
      "get_studio",
      "Get information about a studio by its AniList ID or name",
      {
        studio: z
          .union([z.string(), z.number()])
          .describe("The studio ID or name"),
      },
      {
        title: "Get Studio Information",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ studio }) => {
        try {
          const studioInfo = await anilist.studio(studio);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(studioInfo, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • The handler function for 'get_studio' tool. It takes the studio input, calls anilist.studio(studio), stringifies the result as JSON text content, or returns an error response.
    async ({ studio }) => {
      try {
        const studioInfo = await anilist.studio(studio);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(studioInfo, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Zod input schema for the 'studio' parameter, accepting either string (name) or number (ID).
    studio: z
      .union([z.string(), z.number()])
      .describe("The studio ID or name"),
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. It states it 'gets information' (implying read-only), but doesn't specify what information is returned (e.g., details like founded date, location, media list), error handling for invalid IDs/names, rate limits, authentication requirements, or whether it's idempotent. For a read operation 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 with zero waste. It front-loads the core purpose ('Get information about a studio') and adds necessary specificity ('by its AniList ID or name'). Every word earns its place, making it easy to parse quickly without redundancy.

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 tool's complexity (read operation with 1 parameter), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what information is returned (critical without output schema), error scenarios, or usage context relative to siblings. For a tool in a media API context with many sibling tools, more guidance is needed to ensure correct agent invocation.

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 'studio' documented as 'The studio ID or name' of type string/number. The description adds that it's an 'AniList ID or name', specifying the source context (AniList platform), which provides marginal value beyond the schema. Since schema coverage is high, the baseline is 3, and the description doesn't significantly enhance parameter understanding (e.g., format examples, validation rules).

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 ('Get information') and resource ('about a studio'), specifying it can be retrieved by 'AniList ID or name'. It distinguishes from siblings like 'search_studio' (which likely returns multiple results) by focusing on retrieving a single studio's information. However, it doesn't explicitly contrast with 'favourite_studio' (which modifies preferences) or 'get_staff' (different resource type), leaving some sibling differentiation implicit rather than explicit.

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. It doesn't mention when to choose 'get_studio' over 'search_studio' (for exact vs. fuzzy matching), 'get_anime' (for related media), or 'favourite_studio' (for modifying preferences). There's no context about prerequisites, such as needing a valid studio identifier, or exclusions like handling non-existent studios.

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