AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Get comments on a forum thread

get_thread_comments

Read-only

Retrieve top-level comments from an AniList forum thread by its ID, with pagination. Replies are nested under each parent comment's childComments instead of listed separately.

Instructions

List top-level comments posted on an AniList forum thread, by the thread's ID. Replies (posted via post_thread_comment's parentCommentId) are nested under their parent's childComments rather than appearing as separate entries in this list.

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.
`perPage`	No	Results per page (max 50, AniList's own ceiling — it silently clamps anything higher).
`threadId`	Yes	AniList thread ID — use search_thread to find one, or pass one already known (e.g. from an AniList forum URL, or from get_thread).

Output Schema

Name	Required	Description	Default
`comments`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.0Oct 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed9 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 / comments / properties / pageInfo / properties / hasNextPage / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / comments / properties / pageInfo / properties / hasNextPage / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
removedOutput schema / properties / comments / properties / threadComments / items / properties / comment / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / comments / properties / threadComments / items / properties / comment / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / comments / properties / threadComments / items / properties / isLiked / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / comments / properties / threadComments / items / properties / isLiked / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

changedOutput schema / properties / comments / properties / threadComments / items / properties / user / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "id": {
-        "exclusiveMinimum": 0,
-        "maximum": 2147483647,
-        "type": "integer"
-      },
-      "name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "id"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "id": {
+        "exclusiveMinimum": 0,
+        "maximum": 2147483647,
+        "type": "integer"
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "id"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed13 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
```
addedInput schema / properties / threadId / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / threadId / minimum
```
Removed value: --2147483648
```

addedOutput schema / $defs

Added value: +{
+  "__schema0": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      },
+      {
+        "items": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    ]
+  }
+}

changedOutput schema / properties / comments / properties / threadComments / items / properties / childComments / anyOf

Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/__schema0"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / comments / properties / threadComments / items / properties / id / exclusiveMinimum
```
Added value: +0
```
changedOutput schema / properties / comments / properties / threadComments / items / properties / id / maximum
```
Previous value: -9007199254740991New value: +2147483647
```
removedOutput schema / properties / comments / properties / threadComments / items / properties / id / minimum
```
Removed value: --9007199254740991
```

changedOutput schema / properties / comments / properties / threadComments / items / properties / likeCount / anyOf

Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / comments / properties / threadComments / items / properties / siteUrl / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "uri",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / comments / properties / threadComments / items / properties / user / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "id": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "id"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "id": {
+        "exclusiveMinimum": 0,
+        "maximum": 2147483647,
+        "type": "integer"
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "id"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Addedv0.3.0Jul 26, 2026
Removedv0.2.0Jul 21, 2026
Addedv0.2.0Jul 21, 2026

TDQS

A4.2/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 real behavioral context beyond that: replies are not returned as separate list entries but nested under each parent's childComments field, which materially affects how the agent interprets the response shape.

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, zero waste. The core action and scope come first, and the nesting caveat follows as a tightly scoped second sentence that earns its place by preventing a real misreading of results.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full parameter documentation in the schema, the description doesn't need to explain return values or pagination. It covers scope and the one non-obvious structural behavior (nested replies); the only minor gap is nothing about ordering or page-size limits, which the schema already handles.

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 each parameter (threadId, page, perPage) already carries a detailed description, including pagination ceilings and clamping behavior. The description's only added parameter framing is 'by the thread's ID', which the schema already states. 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 ('List top-level comments posted on an AniList forum thread') and explicitly names the scope ('by the thread's ID'). The 'top-level' qualifier plus the contrast with replies makes it immediately distinguishable from siblings like get_thread and 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?

The description makes clear when this tool applies (fetching a thread's comment list) and points to post_thread_comment as the source of replies, implicitly telling the agent that posting is not this tool's job. It stops short of naming an explicit alternative for reading replies other than noting they arrive nested in the parent entry.

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

Deploy Server