AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Search studios

search_studio

Read-only

Find multiple AniList animation or production studio candidates by name, then retrieve their IDs for detailed studio lookups.

Instructions

Search/browse AniList's animation/production studios by name, when you want to see multiple candidates rather than take the closest match — get_studio's own name param already does this same fuzzy search directly and resolves a partial name on its own. Returns AniList IDs to use with get_studio.

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	Studio name (or part of it) to search for.
`perPage`	No	Results per page (max 50, AniList's own ceiling — it silently clamps anything higher).

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"
+]
```
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 / studios / items / properties / id / exclusiveMinimum
```
Added value: +0
```
- changedOutput schema / properties / results / properties / studios / items / properties / id / maximum
```
Previous value: -9007199254740991New value: +2147483647
```
- removedOutput schema / properties / results / properties / studios / items / properties / id / minimum
```
Removed value: --9007199254740991
```

Changed1 schema field changedv0.4.0Jul 28, 2026

addedOutput schema / properties / results / properties / studios / 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
First observedv0.1.5Jul 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=true and openWorldHint=true, so the safety profile is covered. The description adds non-obvious workflow context by stating the output is AniList IDs meant to be fed into get_studio, which is genuine chaining guidance beyond the structured fields. Pagination limits are left entirely to the schema, which documents them thoroughly.

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?

Two sentences, front-loaded with the action and scope, then the sibling disambiguation. The dense phrasing about get_studio's `name` param earns its length because it prevents a redundant call.

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?

Read-only annotations cover safety, an output schema exists, parameters are fully documented, and the description supplies the sibling routing and the downstream chaining hint. Nothing an agent needs to call this correctly is missing.

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 coverage is 100% and all three parameters carry detailed descriptions, including page-depth limits and the perPage clamp, so the baseline is 3. The description only implies that `term` is a fuzzy partial match; it adds no syntax or format detail the schema doesn't already supply.

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/browse AniList's animation/production studios by name') and immediately distinguishes itself from get_studio by framing the use case as seeing multiple candidates rather than resolving a single closest match. An agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('when you want to see multiple candidates rather than take the closest match') and names the alternative, get_studio, along with the fact that its `name` param already does the same fuzzy resolution. This is exactly the routing information an agent needs between two overlapping search tools.

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

Deploy Server