Skip to main content
Glama
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Search users

search_user
Read-only

Find AniList users by username or partial name to get their user ID for profiles, stats, public lists, or follow actions.

Instructions

Search AniList for users by username. Returns AniList user IDs to use with get_user_profile/get_full_user_info (profile), get_user_stats (statistics), get_user_list (their public list), or toggle_follow_user.

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.
termYesUsername (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_user_profile/get_full_user_info for a single entry's full bio instead.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.9.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_user_profile/get_full_user_info for a single entry's full bio instead.",
+  "type": "boolean"
+}
    • 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 / users / items / properties / id / exclusiveMinimum
      Added value: +0
    • changedOutput schema / properties / results / properties / users / items / properties / id / maximum
      Previous value: -9007199254740991New value: +2147483647
    • removedOutput schema / properties / results / properties / users / items / properties / id / minimum
      Removed value: --9007199254740991
  3. Changed1 schema field changedv0.4.0
    • addedOutput schema / properties / results / properties / users / 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.3/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 description does not need to repeat that this is a safe read-only search. It adds useful behavioral context by explicitly stating that the tool returns AniList user IDs rather than full user profiles, which prevents an agent from expecting complete user data and directs it to the correct follow-up tools.

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?

The entire description is a single dense sentence that front-loads the action ('Search AniList for users') and then packs the return-value contract and downstream tool routing into the rest. Every clause earns its place; the long list of target tools is justified because it is exactly what an agent needs to decide what to do with the result.

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?

For a read-only search tool with 100% schema coverage, an output schema, and readOnlyHint/openWorldHint annotations, the description is complete. It states what is searched, how to search, what is returned, and how to use the returned IDs. There is no missing piece an agent would need to invoke the tool correctly.

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 the schema already documents term, page, perPage, and includeDescription with detailed explanations. The description adds no new parameter-level meaning beyond 'by username,' which is also in the term schema. Per the rubric, baseline 3 is appropriate when the schema carries the burden.

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 opens with a specific verb and resource: 'Search AniList for users by username.' This clearly differentiates search_user from the many sibling search tools (search_media, search_character, search_staff, etc.) that target different entity types. It also clarifies the output purpose by saying it returns user IDs, reinforcing what the tool does rather than restating the name.

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?

The description gives clear downstream context: returned IDs can be passed to get_user_profile/get_full_user_info, get_user_stats, get_user_list, or toggle_follow_user. This helps an agent know what to do after calling the tool. It does not explicitly state when not to use search_user, but the entity-specific wording and the list of sibling search tools make the intended use reasonably clear.

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