AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Get comments on a forum thread

get_thread_comments

Read-only

Fetch top-level comments from an AniList forum thread by its ID, with replies nested under their parents for easy browsing.

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

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
`comments`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds valuable behavioral detail beyond that: replies are nested under their parent's childComments rather than appearing as separate entries, which materially affects how an agent should interpret results.

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 concise sentences, with the primary purpose front-loaded and the key behavioral nuance about nested replies following immediately. Every sentence earns its place with no filler.

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 rich schema, read-only annotations, and an output schema for return values, nothing essential is missing. The description clarifies the only non-obvious behavior an agent needs to correctly interpret the results: the top-level vs. nested reply distinction.

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?

The input schema provides 100% coverage, including rich context on pagination limits and how to obtain a threadId. The description adds only minor framing by mentioning the thread ID and parentCommentId; the schema carries the load, so the baseline of 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?

The description states a specific verb and resource: 'List top-level comments posted on an AniList forum thread, by the thread's ID.' It distinguishes itself from sibling tools like get_thread (which fetches the thread itself) and post_thread_comment (which posts comments), and clarifies that only top-level comments are returned.

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 this tool returns top-level comments only and that replies are nested under childComments, referencing the related post_thread_comment tool. It gives clear context for what results will look like, though it does not explicitly state when to choose this over an alternative such as get_thread.

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

Deploy Server