Skip to main content
Glama

get_staff

Retrieve detailed information about AniList staff members using their ID or name, accessed via the AniList MCP server for API data integration.

Instructions

Get information about staff member by their AniList ID or name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe AniList ID or name of the staff member

Implementation Reference

  • The handler function that implements the core logic of the 'get_staff' tool by querying AniList for staff information based on the provided ID or name and returning formatted JSON or error.
    async ({ id }) => {
      try {
        const staff = await anilist.people.staff(id);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(staff, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • The Zod input schema for the 'get_staff' tool, validating the 'id' parameter as either a number or string.
    {
      id: z
        .union([z.number(), z.string()])
        .describe("The AniList ID or name of the staff member"),
    },
  • The direct registration of the 'get_staff' tool using server.tool() within the registerPeopleTools function, including name, description, schema, hints, and handler.
    server.tool(
      "get_staff",
      "Get information about staff member by their AniList ID or name",
      {
        id: z
          .union([z.number(), z.string()])
          .describe("The AniList ID or name of the staff member"),
      },
      {
        title: "Get Staff Member Info",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ id }) => {
        try {
          const staff = await anilist.people.staff(id);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(staff, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • tools/index.ts:35-35 (registration)
    Call to registerPeopleTools inside registerAllTools, which triggers the registration of 'get_staff'.
    registerPeopleTools(server, anilist, config);
  • index.ts:61-61 (registration)
    Top-level call to registerAllTools in the main index.ts, which ultimately registers the 'get_staff' tool.
    registerAllTools(server, anilist, config);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets information' but doesn't specify what information is returned (e.g., biography, roles), whether it requires authentication, rate limits, or error handling. This is a significant gap for a tool with no annotation coverage.

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 and parameter context, making it easy to parse without unnecessary elaboration.

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 and no output schema, the description is incomplete. It doesn't explain what information is returned (e.g., fields like name, biography, works), error cases (e.g., invalid ID), or behavioral traits like authentication needs. For a read operation with rich sibling tools, this leaves the agent under-informed.

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 parameter 'id' documented as 'The AniList ID or name of the staff member'. The description adds minimal value beyond this, merely restating 'by their AniList ID or name'. 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 'Get' and resource 'information about staff member', specifying it retrieves data by 'AniList ID or name'. It distinguishes from siblings like 'search_staff' by focusing on retrieval by identifier rather than search queries, though it doesn't explicitly contrast with 'get_todays_birthday_staff' which has a different scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the parameter specification (ID or name), suggesting it's for looking up specific staff members. However, it lacks explicit guidance on when to use this versus alternatives like 'search_staff' (for broader searches) or 'get_todays_birthday_staff' (for birthday-specific data), leaving some ambiguity for the agent.

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