AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Search staff

search_staff

Read-only

Search AniList staff members by name to retrieve their IDs for use with get_staff. Bios are omitted by default unless includeDescription is enabled.

Instructions

Search AniList for staff members by name. Returns AniList IDs to use with get_staff. Each result's bio (description) is omitted unless you set includeDescription.

Input Schema

Name	Required	Description
`page`	No	Page number for pagination. AniList's paginated connections (search results, a title's characters/staff/reviews, activity feeds, forum comments) reject a page whose page × perPage exceeds ~5000 entries with an upstream error, so paging that deep fails rather than returning more results.
`term`	Yes	Staff member name (or part of it) to search for.
`perPage`	No	Results per page (max 50, AniList's own ceiling — it silently clamps anything higher).
`includeDescription`	No	Also fetch each result's full bio (`description`). Kept off by default — a bio can run to several thousand characters, and always including it would burn tokens on text you may not need; use get_staff for a single entry's full bio instead.

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.0Oct 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed4 schema fields changedv0.9.0Sep 27, 2026
- changedInput schema / properties / perPage / description
```
Previous value: -"Results per page (max 25)."New value: +"Results per page (max 50, AniList's own ceiling — it silently clamps anything higher)."
```
- changedInput schema / properties / perPage / maximum
```
Previous value: -25New value: +50
```
- removedOutput schema / properties / results / properties / pageInfo / properties / hasNextPage / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / properties / pageInfo / properties / hasNextPage / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

Changed1 schema field changedv0.8.0Aug 17, 2026

addedInput schema / properties / includeDescription

Added value: +{
+  "default": false,
+  "description": "Also fetch each result's full bio (`description`). Kept off by default — a bio can run to several thousand characters, and always including it would burn tokens on text you may not need; use get_staff for a single entry's full bio instead.",
+  "type": "boolean"
+}

Changed6 schema fields changedv0.7.1Aug 1, 2026
- changedInput schema / properties / page / description
```
Previous value: -"Page number for pagination."New value: +"Page number for pagination. AniList's paginated connections (search results, a title's characters/staff/reviews, activity feeds, forum comments) reject a page whose page × perPage exceeds ~5000 entries with an upstream error, so paging that deep fails rather than returning more results."
```
- addedInput schema / properties / perPage / exclusiveMinimum
```
Added value: +0
```
- removedInput schema / properties / perPage / minimum
```
Removed value: -1
```
- addedOutput schema / properties / results / properties / staff / items / properties / id / exclusiveMinimum
```
Added value: +0
```
- changedOutput schema / properties / results / properties / staff / items / properties / id / maximum
```
Previous value: -9007199254740991New value: +2147483647
```
- removedOutput schema / properties / results / properties / staff / items / properties / id / minimum
```
Removed value: --9007199254740991
```

Changed1 schema field changedv0.4.0Jul 28, 2026

addedOutput schema / properties / results / properties / staff / items / description

Added value: +"Only `id` is guaranteed here — the real object has more fields, but their shape depends on which variant of an underlying union type this is (e.g. which activity type), so only the field common to every variant is declared."

Addedv0.3.0Jul 26, 2026
Removedv0.2.0Jul 21, 2026
Addedv0.2.0Jul 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond that: results' bios are omitted by default and must be opted into, which affects token cost and downstream calls.

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?

Three short sentences: purpose first, then the ID hand-off, then the one non-obvious default. No filler, and the most actionable constraint is front-loaded.

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?

An output schema exists and annotations cover safety, so the description needn't explain return shapes. Combined with rich parameter docs, an agent has everything needed to pick and call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning by explaining that each result's `description` field is omitted unless `includeDescription` is set — context the schema states more tersely. It does not address pagination, but the schema covers that thoroughly.

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 and resource ('Search AniList for staff members by name') and immediately frames the output's purpose (IDs for get_staff). This cleanly distinguishes it from sibling get_staff and from search_character/search_user/search_studio.

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

Usage Guidelines4/5

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

Explicitly routes the agent: use this to obtain IDs, then call get_staff, and use get_staff directly for a single entry's full bio. It gives a clear context but stops short of stating exclusions such as when not to search at all or how it compares to get_todays_birthdays-style browsing.

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

Deploy Server