AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Search forum threads

search_thread

Read-only

Find AniList forum threads by title/body text, category, or related media, and return thread IDs for reading or posting comments.

Instructions

Search/browse AniList's forum threads by title/body text and/or restrict to one category. Returns AniList thread IDs (with title/category for context) to use with get_thread, get_thread_comments, post_thread, or post_thread_comment.

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`	No	Free-text search term (matches thread title/body); results are relevance-ranked. Omit to browse, most recently replied-to first.
`perPage`	No	Results per page (max 50, AniList's own ceiling — it silently clamps anything higher).
`categoryId`	No	Restrict to this forum category ID. Not independently listable by any tool — resolve one from a thread you've already read (its `categories` field) or from a forum URL like anilist.co/forum/recent?category=<id>. A wrong or nonexistent ID doesn't error, it silently filters to an empty result — indistinguishable from 'no threads in this category.'
`mediaCategoryId`	No	Restrict to threads tagged with this AniList anime/manga ID (from search_media/get_media). A nonexistent ID errors as not found.

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.11.0Oct 25, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / mediaCategoryId / description

Previous value: -"Restrict to threads tagged with this AniList anime/manga ID (from search_media/get_media). Not existence-checked: a nonexistent media ID doesn't error, it silently filters to an empty result — resolve the ID via search_media first if you need to confirm the title actually exists."New value: +"Restrict to threads tagged with this AniList anime/manga ID (from search_media/get_media). A nonexistent ID errors as not found."

changedInput schema / properties / term / description

Previous value: -"Free-text search term (matches thread title/body). Omit to just filter/browse."New value: +"Free-text search term (matches thread title/body); results are relevance-ranked. Omit to browse, most recently replied-to first."

addedInput schema / properties / term / minLength
```
Added value: +1
```

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"
+]
```
Changed10 schema fields changedv0.7.1Aug 1, 2026
- addedInput schema / properties / categoryId / exclusiveMinimum
```
Added value: +0
```
- removedInput schema / properties / categoryId / minimum
```
Removed value: --2147483648
```
- addedInput schema / properties / mediaCategoryId / exclusiveMinimum
```
Added value: +0
```
- removedInput schema / properties / mediaCategoryId / minimum
```
Removed value: --2147483648
```
- 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 / threads / items / properties / id / exclusiveMinimum
```
Added value: +0
```
- changedOutput schema / properties / results / properties / threads / items / properties / id / maximum
```
Previous value: -9007199254740991New value: +2147483647
```
- removedOutput schema / properties / results / properties / threads / items / properties / id / minimum
```
Removed value: --9007199254740991
```

Changed3 schema fields changedv0.4.0Jul 28, 2026

changedInput schema / properties / categoryId / description

Previous value: -"Restrict to this forum category ID. Not independently listable by any tool — resolve one from a thread you've already read (its `categories` field) or from a forum URL like anilist.co/forum/recent?category=<id>."New value: +"Restrict to this forum category ID. Not independently listable by any tool — resolve one from a thread you've already read (its `categories` field) or from a forum URL like anilist.co/forum/recent?category=<id>. A wrong or nonexistent ID doesn't error, it silently filters to an empty result — indistinguishable from 'no threads in this category.'"

changedInput schema / properties / mediaCategoryId / description

Previous value: -"Restrict to threads tagged with this AniList anime/manga ID (from search_media/get_media)."New value: +"Restrict to threads tagged with this AniList anime/manga ID (from search_media/get_media). Not existence-checked: a nonexistent media ID doesn't error, it silently filters to an empty result — resolve the ID via search_media first if you need to confirm the title actually exists."

addedOutput schema / properties / results / properties / threads / 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."

First observedv0.1.5Jul 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With readOnlyHint=true and openWorldHint=true already present, the description adds useful behavioral context: it returns AniList thread IDs plus title/category and is intended as a lookup step before get/post tools. It does not cover rate limits or auth needs, but it does not contradict the annotations and adds practical result-handling context.

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 definition is two compact sentences, front-loaded with the core search/browse behavior and followed by return/usage context. Every sentence contributes useful selection or follow-up information.

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 full schema coverage, existing output schema, and read-only/open-world annotations, the description supplies everything an agent needs at a high level: what is searched, how browsing works, what is returned, and which tools consume the results.

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 five parameters are already fully documented. The description restates the high-level filtering model (title/body text and/or category), but adds little syntax or edge-case detail beyond what the schema already provides.

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 specific verbs (Search/browse) and a specific resource (AniList forum threads), plus scope qualifiers (title/body text, category restriction). It also distinguishes the result from direct thread retrieval by saying the returned IDs are meant for get_thread, get_thread_comments, post_thread, or post_thread_comment.

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?

It clearly explains that omitting the term browses threads and that returned IDs feed specific follow-up tools, which gives strong usage context. It does not explicitly state when not to use this tool versus siblings like get_thread, but the path from search to retrieval is clear.

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

Deploy Server