Fetch an anime or manga character profile by AniList ID, returning names, image, bio, traits, favourites, and titles with billed roles.
Get an anime/manga character. Returns a character profile by AniList id: names, image, description, gender, age, blood type, birthday, favourites, and the titles the character appears in with their billed role.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | AniList character id |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the complete set of returned fields (names, image, description, gender, age, blood type, birthday, favourites, and billed roles in titles), which is meaningful output transparency absent an output schema. It omits auth requirements and error behavior for invalid ids.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the purpose and followed by the return payload. No filler, though the field enumeration in the second sentence is dense enough to approach list-dumping.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, spelling out the returned profile fields is exactly the right compensation, and the id-keyed scope is stated. It stops short of covering error cases or pointing at the search sibling to obtain an id.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Single parameter with 100% schema description coverage, so the schema already documents the 'id' argument. The description's 'by AniList id' reinforces but does not extend the schema; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('anime/manga character'), then pins the exact lookup key ('by AniList id'). This clearly distinguishes it from sibling anime_character_search, which would resolve a name to an id rather than fetch a profile.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'by AniList id' implies this is an id-based lookup that presupposes a prior search, but the description never names anime_character_search or states when to prefer one over the other. Usage is inferable rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.