Skip to main content
Glama
Sign In
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Post a comment on a forum thread

post_thread_comment

Post a new comment on an AniList forum thread or update an existing one by comment ID. Supports replies via parent comment ID and markdown text.

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

NameRequiredDescriptionDefault
idNoComment ID to update instead of creating a new one. Not the comment you're replying to — that's `parentCommentId`.
commentYesThe comment text to post (markdown; per AniList's own schema, up to 12000 characters).
threadIdYesAniList thread ID to comment on (from get_thread/search_thread).
parentCommentIdNoReply 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

NameRequiredDescriptionDefault
commentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed4 schema fields changedv0.9.0
    • 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"
+]
  3. Changed13 schema fields changedv0.7.1
    • 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"
+  }
+]
  4. Changed2 schema fields changedv0.5.0
    • 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
  5. Addedv0.3.0
  6. Removedv0.2.0
  7. Changed3 schema fields changedv0.2.0
    • 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"
+    }
+  ]
+}
  8. First observedv0.1.5

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds the genuine, non-annotated context that authentication is required and that the comment is attributed to the authenticated user. It says nothing about ownership rules for edits, notifications, or rate limits, so the added value is modest but real.

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?

A single sentence with the authentication prerequisite front-loaded and the update mode appended; no redundant restatement of the title or schema.

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?

An output schema exists, so return values need no explanation, and annotations plus the auth note cover the interaction contract. It is only slightly short of complete because editing someone else's comment versus one's own is unaddressed for a mutation tool.

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%, and the schema itself already explains `id` vs `parentCommentId`, thread IDs, and the markdown character limit in detail. The description only reinforces the `id` = update behavior already documented in the schema, so 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 ('Post a new comment on an AniList forum thread') and disambiguates the create-vs-update behavior in the same sentence. An agent can distinguish it from delete_thread_comment and post_thread without opening any schema.

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 '[Requires login]' prefix and 'from the authenticated user's account' establish the prerequisite, and the description explicitly says to use `id` to update rather than create. It does not name a sibling alternative or state when this should be chosen over post_thread, so it stops short of full routing guidance.

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