Skip to main content
Glama
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Search studios

search_studio
Read-only

Find AniList studios by partial name to get their IDs for later lookup. Returns multiple matching candidates for disambiguation.

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

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage 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.
termYesStudio name (or part of it) to search for.
perPageNoResults per page (max 50, AniList's own ceiling — it silently clamps anything higher).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • 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"
+]
  2. Changed6 schema fields changedv0.7.1
    • 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
  3. Changed1 schema field changedv0.4.0
    • 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."
  4. Addedv0.3.0
  5. Removedv0.2.0
  6. First observedv0.1.5

TDQS

A4.4/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, and the description adds relevant behavioral context: it returns multiple candidate matches and provides AniList IDs for use with get_studio. It does not contradict the annotations and does not need to re-explain read-only semantics.

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?

The description is front-loaded with the core purpose and wastes no words, though the second sentence is slightly dense with comparative detail. Overall it is compact and readable.

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?

Given the output schema exists, pagination is documented in the input schema, and annotations cover the read-only/open-world profile, the description is complete enough for an agent to select and invoke the tool correctly. It covers purpose, use case, output relationship, and key alternative.

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 the schema already documents term, page, and perPage in detail including defaults, limits, and upstream paging behavior. The description reinforces term as a partial-name search but does not add meaning beyond the schema's parameter descriptions.

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?

The description uses a specific verb-resource pair ('Search/browse AniList's animation/production studios by name') and explicitly contrasts itself with get_studio, which takes the closest match. This clearly differentiates it from its sibling search tools.

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?

It gives an explicit when-to-use condition: when you want multiple candidates rather than the closest match. It also names the alternative (get_studio) and explains that get_studio's own name param already performs fuzzy matching, so an agent can decide correctly without opening either schema.

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