Skip to main content
Glama
Sign In
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Search characters

search_character
Read-only

Search AniList characters by name to retrieve AniList IDs for use with get_character, with optional bio descriptions when needed.

Instructions

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

Input 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.
termYesCharacter name (or part of it) to search for.
perPageNoResults per page (max 50, AniList's own ceiling — it silently clamps anything higher).
includeDescriptionNoAlso 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_character for a single entry's full bio instead.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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"
+]
  3. Changed1 schema field changedv0.8.0
    • 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_character for a single entry's full bio instead.",
+  "type": "boolean"
+}
  4. 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 / characters / items / properties / id / exclusiveMinimum
      Added value: +0
    • changedOutput schema / properties / results / properties / characters / items / properties / id / maximum
      Previous value: -9007199254740991New value: +2147483647
    • removedOutput schema / properties / results / properties / characters / items / properties / id / minimum
      Removed value: --9007199254740991
  5. Changed1 schema field changedv0.4.0
    • addedOutput schema / properties / results / properties / characters / 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."
  6. Addedv0.2.0
  7. Removedv0.2.0
  8. First observedv0.1.5

TDQS

A4.3/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 description usefully builds on them by disclosing output behavior: IDs are returned for follow-up calls and each result's `description` field is withheld unless the flag is set. The token-cost rationale adds genuine context. It leaves pagination depth limits to the schema, which is a minor omission rather than a gap.

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 tight sentences with no redundancy: purpose first, then the follow-up tool, then the one non-obvious output toggle. Nothing is buried or repeated.

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?

With an output schema present, rich annotation coverage, and 100% schema descriptions, the description only needs to orient the agent — which it does by naming the resource, the returned ID, and the omitted bio field. Nothing needed 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 description coverage is 100%, so all four parameters are already fully documented upstream, including the perPage ceiling and the page × perPage limit. The description only restates the includeDescription default and term-by-name semantics, adding little beyond what the schema provides; baseline 3 applies.

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 characters by name') and immediately contrasts with the sibling get_character by saying it returns IDs for use with it. An agent can distinguish this from search_media, search_staff, and search_studio purely from the description.

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?

Clearly positions the tool as a discovery step feeding into get_character, and names get_character as the alternative when a single full bio is needed. It stops short of explicit 'do not use for X' exclusions, but the routing between search and fetch is unambiguous.

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