Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

anime_title_staff

Fetch an anime's staff credits using its AniList ID, returning names, roles, occupations, images, and paginated results.

Instructions

List an anime's staff. Lists the people credited on an anime by its AniList anime id. Each person has name, native_name, role (their production role), occupations, image and site_url. Paged with page (default 1) and per_page (default 10, max 50), with total and has_next_page.

Input Schema

NameRequiredDescriptionDefault
idYesAniList anime id
pageNo1-based page number, default 1
per_pageNoResults per page, default 10, max 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. Addedv1.5.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned fields (name, native_name, role, occupations, image, site_url) and fully specifies pagination (page default 1, per_page default 10 max 50, total and has_next_page). It stops short of stating read-only/idempotent semantics or rate limits, but for a list endpoint this is solid disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and compact, with the return fields and pagination details packed efficiently. The opening two sentences ('List an anime's staff.' / 'Lists the people credited...') are slightly redundant, which is the only thing keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must cover return values, and it does by listing all person fields plus pagination metadata. For a simple three-parameter list tool this is complete enough to call correctly.

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 id, page, and per_page. The description restates the defaults and the max-50 cap, adding marginal value but nothing the schema lacks; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('List an anime's staff') and immediately clarifies it returns people credited on an anime keyed by AniList id. This clearly distinguishes it from the sibling anime_title_characters (cast vs crew) and manga_title_staff.

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 only implied: an agent can infer you call this to get production staff for a known anime id. There is no explicit when-to-use/when-not guidance and no mention of the sibling anime_title, anime_title_characters, or anime_title_recommendations as alternatives to choose between.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools