AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Post a forum thread

post_thread

Create or update an AniList forum thread on the authenticated account. Provide a thread ID to edit an existing post, or omit it to publish a new one.

Instructions

[Requires login] Post a new forum thread to the authenticated user's own AniList account, or update an existing one by passing its id. Use search_thread first if you want to check whether a similar thread already exists before posting a new one. Note: this tool's own response doesn't include categories/mediaCategories/isSticky/isLocked — call get_thread with the returned id afterward to confirm whether a category/sticky/locked change actually applied, especially since sticky/locked can silently no-op and categories/mediaCategories can silently drop existing values (see those fields' own descriptions below).

Input Schema

Name	Required	Description
`id`	No	Thread ID to update instead of creating a new one.
`body`	No	Thread body (markdown; per AniList's own schema, up to 30000 characters) — REQUIRED when creating a new thread, optional when updating one via `id` (confirmed live: omitting it on an update leaves the existing body unchanged).
`title`	No	Thread title (per AniList's own schema: 6-120 characters) — REQUIRED when creating a new thread, optional when updating one via `id` (confirmed live: omitting it on an update leaves the existing title unchanged, it isn't cleared).
`locked`	No	Lock this thread to prevent further replies (only takes effect if you have moderator permission — confirmed live that a non-mod account's own thread silently stays unlocked).
`sticky`	No	Pin this thread (only takes effect if you have moderator permission — confirmed live that a non-mod account's own thread silently stays unpinned).
`categories`	No	Forum category IDs to post this thread under — REQUIRED when creating a new thread (AniList rejects the mutation otherwise), optional when updating one via `id`. When updating and you DO set this, it's a full replace, not a merge — confirmed live: an existing thread with categories [A] updated with just [B] ended up with [B] only, A silently dropped. Fetch the thread's current categories first (get_thread) and include every one you want to keep. Not independently listable by any tool; resolve one from a thread you've already read (get_thread's/search_thread's `categories` field) or from a forum URL like anilist.co/forum/recent?category=<id>.
`mediaCategories`	No	AniList anime/manga IDs to tag this thread with, for threads about a specific title (from search_media/get_media). Optional on both create and update. When updating and you DO set this, it's a full replace, not a merge — confirmed live: an existing thread tagged with [A] updated with just [B] ended up with [B] only, A silently dropped (same behavior as `categories` above). Fetch the thread's current `mediaCategories` first (get_thread) if you need to keep an existing tag alongside a new one.

Output Schema

Name	Required	Description	Default
`thread`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.0Oct 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed4 schema fields changedv0.9.0Sep 27, 2026
- removedOutput schema / properties / thread / properties / isLiked / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / thread / properties / isLiked / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / properties / thread / properties / title / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / thread / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed19 schema fields changedv0.7.1Aug 1, 2026

changedInput schema / properties / body / description

Previous value: -"Thread body (markdown; per AniList's own schema, up to 30000 characters)."New value: +"Thread body (markdown; per AniList's own schema, up to 30000 characters) — REQUIRED when creating a new thread, optional when updating one via `id` (confirmed live: omitting it on an update leaves the existing body unchanged)."

changedInput schema / properties / categories / description

Previous value: -"Forum category IDs to post this thread under — needed when creating a new thread. Not independently listable by any tool; resolve one from a thread you've already read (get_thread's/search_thread's `categories` field) or from a forum URL like anilist.co/forum/recent?category=<id>."New value: +"Forum category IDs to post this thread under — REQUIRED when creating a new thread (AniList rejects the mutation otherwise), optional when updating one via `id`. When updating and you DO set this, it's a full replace, not a merge — confirmed live: an existing thread with categories [A] updated with just [B] ended up with [B] only, A silently dropped. Fetch the thread's current categories first (get_thread) and include every one you want to keep. Not independently listable by any tool; resolve one from a thread you've already read (get_thread's/search_thread's `categories` field) or from a forum URL like anilist.co/forum/recent?category=<id>."

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

changedInput schema / properties / mediaCategories / description

Previous value: -"AniList anime/manga IDs to tag this thread with, for threads about a specific title (from search_media/get_media)."New value: +"AniList anime/manga IDs to tag this thread with, for threads about a specific title (from search_media/get_media). Optional on both create and update. When updating and you DO set this, it's a full replace, not a merge — confirmed live: an existing thread tagged with [A] updated with just [B] ended up with [B] only, A silently dropped (same behavior as `categories` above). Fetch the thread's current `mediaCategories` first (get_thread) if you need to keep an existing tag alongside a new one."

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

changedInput schema / properties / sticky / description

Previous value: -"Pin this thread (only takes effect if you have moderator permission)."New value: +"Pin this thread (only takes effect if you have moderator permission — confirmed live that a non-mod account's own thread silently stays unpinned)."

changedInput schema / properties / title / description

Previous value: -"Thread title (per AniList's own schema: 6-120 characters)."New value: +"Thread title (per AniList's own schema: 6-120 characters) — REQUIRED when creating a new thread, optional when updating one via `id` (confirmed live: omitting it on an update leaves the existing title unchanged, it isn't cleared)."

removedInput schema / required

Removed value: -[
-  "title",
-  "body"
-]

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

changedOutput schema / properties / thread / 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 / thread / properties / replyCount / anyOf

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

changedOutput schema / properties / thread / properties / siteUrl / anyOf

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

changedOutput schema / properties / thread / properties / viewCount / anyOf

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

Changed5 schema fields changedv0.5.0Jul 29, 2026

changedInput schema / properties / body / description

Previous value: -"Thread body (markdown)."New value: +"Thread body (markdown; per AniList's own schema, up to 30000 characters)."

addedInput schema / properties / body / maxLength
```
Added value: +30000
```

changedInput schema / properties / title / description

Previous value: -"Thread title."New value: +"Thread title (per AniList's own schema: 6-120 characters)."

addedInput schema / properties / title / maxLength
```
Added value: +120
```
changedInput schema / properties / title / minLength
```
Previous value: -1New value: +6
```

Addedv0.3.0Jul 26, 2026
Removedv0.2.0Jul 21, 2026
First observedv0.1.5Jul 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent, open-world), and the description adds genuinely valuable behavioral facts: sticky/locked can silently no-op without moderator permission, and categories/mediaCategories are full replaces that drop existing values silently. What holds it back from a 5 is that much of the category-drop detail is duplicated verbatim from the schema field descriptions rather than adding new information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core create/update distinction, and every sentence carries operational weight. It's dense but a bit repetitive, restating the categories-drop caveat already present in the schema, and the parenthetical 'see those fields' own descriptions below' is mildly awkward.

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 7-parameter mutation with an output schema, the description covers the gaps that structured data cannot: that the response omits categories/sticky/locked and that a follow-up get_thread read is needed to confirm application. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns extra credit for summarizing the critical semantic — that `id` switches the tool from create to update mode and that create-vs-update changes which fields are required. It does, however, point to field descriptions 'below' rather than adding materially new semantics for locked/sticky.

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 forum thread') and clarifies dual semantics: create by default, update when `id` is supplied. It's clearly separable from siblings like delete_thread, get_thread, and search_thread.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit before/after guidance: use search_thread first to check for duplicates, and call get_thread afterward to verify category/sticky/locked changes. It also states the login requirement, which gates use entirely.

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

Deploy Server