discord-mcp

channels_forum_create_thread

Create a new Discord forum or media thread with an initial message in one request, enabling programmatic forum posts and Q&A onboarding flows.

Instructions

Purpose: Create a new forum (or media) thread with an initial message in one request.

When to use:

Forum-channel onboarding flows; programmatic question/answer post creation.

When NOT to use:

Anchored thread on an existing message → use messages_create_thread.
Plain text channels - Discord rejects.

Body shape: requires nested message (the initial post). At least one of message.content, message.embeds, or message.components must be present.

Returns: {thread_id, parent_id, message_id, applied_tags?}. Post tag IDs are preserved when returned by Discord.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Thread (post) name (1-100 chars)
`message`	Yes	Initial forum post body. At least one of content/embeds/components required.
`channel_id`	Yes	Parent forum/media channel
`applied_tags`	No	Forum tag IDs to apply to the thread
`audit_reason`	No	Reason recorded in audit log (X-Audit-Log-Reason header)
`rate_limit_per_user`	No
`auto_archive_duration`	No	Auto-archive after N minutes (60, 1440, 4320, or 10080)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "message_id": {
-        "anyOf": [
-          {
-            "description": "Discord message ID",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "parent_id": {
-        "anyOf": [
-          {
-            "description": "Discord channel ID (snowflake)",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "thread_id": {
-        "description": "Discord channel ID (snowflake)",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "thread_id",
-      "parent_id",
-      "message_id"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "applied_tags": {
+        "description": "Tag IDs applied to a forum/media post, when returned by Discord",
+        "items": {
+          "pattern": "^\\d{17,20}$",
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "message_id": {
+        "anyOf": [
+          {
+            "description": "Discord message ID",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "parent_id": {
+        "anyOf": [
+          {
+            "description": "Discord channel ID (snowflake)",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "thread_id": {
+        "description": "Discord channel ID (snowflake)",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "thread_id",
+      "parent_id",
+      "message_id"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations provide readOnlyHint=false and destructiveHint=false, so the description isn't required to restate those. It adds valuable context: the need for a nested message with at least one of content/embeds/components, the return shape including applied_tags, and the note that tag IDs are preserved. It doesn't contradict annotations and goes beyond them by describing the required body shape and return behavior.

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 well-structured with bold headers, front-loads the core purpose, and each sentence earns its place. It's concise yet covers purpose, exclusions, body shape, and return—no fluff.

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 tool's complexity (nested message, 7 params, output schema present), the description is complete: it covers when to use, when not, body requirements, and return details. The output schema already documents return structure, so the description doesn't need to repeat it. Nothing essential is missing for an agent to call it correctly.

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 86%, so most parameters are already documented. The description adds meaning beyond the schema by stating the nested message requirement and the at-least-one constraint on content/embeds/components, which the schema's individual descriptions don't enforce. It also clarifies applied_tags behavior in the return, adding semantic value.

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 opens with a specific verb and resource: 'Create a new forum (or media) thread with an initial message in one request.' It clearly distinguishes itself from the sibling messages_create_thread by explicitly naming it and contrasting the anchored-thread use case, so an agent can tell them apart immediately.

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?

Includes dedicated 'When to use' and 'When NOT to use' sections. It states the intended scenario (forum-channel onboarding, Q&A posts) and explicitly routes to messages_create_thread for anchored threads, plus warns against plain text channels. This is model usage guidance with exclusions and alternatives.

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

Deploy Server