AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Post a comment on a forum thread

post_thread_comment

Post a new comment or update an existing one on an AniList forum thread after logging in. Provide the thread ID and comment text, with optional reply or edit targets.

Instructions

[Requires login] Post a new comment on an AniList forum thread from the authenticated user's account, or update an existing one by passing its id.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Comment ID to update instead of creating a new one. Not the comment you're replying to — that's `parentCommentId`.
`comment`	Yes	The comment text to post (markdown; per AniList's own schema, up to 12000 characters).
`threadId`	Yes	AniList thread ID to comment on (from get_thread/search_thread).
`parentCommentId`	No	Reply to this specific comment instead of posting top-level (from get_thread_comments). The reply then appears nested under that comment's `childComments` in get_thread_comments, not as a new top-level entry. Not the comment being edited — that's `id`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`comment`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.9.0Sep 27, 2026
- removedOutput schema / properties / comment / properties / comment / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / comment / properties / comment / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / comment / properties / isLiked / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / comment / properties / isLiked / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

Changed13 schema fields changedv0.7.1Aug 1, 2026

changedInput schema / properties / id / description

Previous value: -"Comment ID to update instead of creating a new one."New value: +"Comment ID to update instead of creating a new one. Not the comment you're replying to — that's `parentCommentId`."

addedInput schema / properties / id / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / id / minimum
```
Removed value: --2147483648
```

changedInput schema / properties / parentCommentId / description

Previous value: -"Reply to this specific comment instead of posting top-level (from get_thread_comments). The reply then appears nested under that comment's `childComments` in get_thread_comments, not as a new top-level entry."New value: +"Reply to this specific comment instead of posting top-level (from get_thread_comments). The reply then appears nested under that comment's `childComments` in get_thread_comments, not as a new top-level entry. Not the comment being edited — that's `id`."

addedInput schema / properties / parentCommentId / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / parentCommentId / minimum
```
Removed value: --2147483648
```
addedInput schema / properties / threadId / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / threadId / minimum
```
Removed value: --2147483648
```
addedOutput schema / properties / comment / properties / id / exclusiveMinimum
```
Added value: +0
```
changedOutput schema / properties / comment / properties / id / maximum
```
Previous value: -9007199254740991New value: +2147483647
```
removedOutput schema / properties / comment / properties / id / minimum
```
Removed value: --9007199254740991
```

changedOutput schema / properties / comment / 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 / comment / properties / siteUrl / anyOf

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

Changed2 schema fields changedv0.5.0Jul 29, 2026

changedInput schema / properties / comment / description

Previous value: -"The comment text to post (markdown)."New value: +"The comment text to post (markdown; per AniList's own schema, up to 12000 characters)."

addedInput schema / properties / comment / maxLength
```
Added value: +12000
```

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

Changed3 schema fields changedv0.2.0Jul 21, 2026

changedInput schema / properties / parentCommentId / description

Previous value: -"Reply to this specific comment instead of posting top-level (from get_thread_comments)."New value: +"Reply to this specific comment instead of posting top-level (from get_thread_comments). The reply then appears nested under that comment's `childComments` in get_thread_comments, not as a new top-level entry."

addedOutput schema / properties / comment / properties / isLiked

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / comment / properties / likeCount

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedv0.1.5Jul 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already convey that this is a mutating, non-destructive operation. The description adds the login requirement and clarifies that the action is tied to the authenticated user's account, which is useful operational context beyond the annotations.

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 description is a single, compact sentence with no filler. It front-loads the login requirement and clearly states both creation and update behaviors.

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 4-parameter tool with 100% schema coverage, helpful per-parameter descriptions, an output schema, and annotations covering mutation/destructiveness, the description is sufficiently complete. The only missing element—the reply behavior—is fully documented in `parentCommentId`'s schema description.

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%, with each parameter already well-documented, including the non-obvious distinction between `id` and `parentCommentId`. The description only adds marginal value by mentioning the update behavior via `id`, which the schema already explains.

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 clearly states the verb (post), the resource (comment on an AniList forum thread), and adds the distinction between creating a new comment and updating an existing one via `id`. This differentiates it from siblings like post_thread (posting a thread) and delete_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description notes the login prerequisite and the create-vs-update distinction, giving some usage context. However, it does not explicitly state when to choose this tool over alternatives such as posting an activity, nor does it mention the reply option via `parentCommentId`.

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

Deploy Server