discord-mcp

channels_create_guild_channel

Create new Discord guild channels (text, voice, forum, etc.) with permissions and settings, enabling programmatic server setup and role-based channel provisioning.

Instructions

Purpose: Create a new channel in a guild (text, voice, category, announcement, forum, etc.).

When to use:

Programmatic guild bootstrap; tier-based channel provisioning.

When NOT to use:

Threads - use messages_create_thread, channels_forum_create_thread, or thread-specific tools.

Type values (from Discord API): 0 GUILD_TEXT, 2 GUILD_VOICE, 4 GUILD_CATEGORY, 5 GUILD_ANNOUNCEMENT, 13 GUILD_STAGE_VOICE, 14 GUILD_DIRECTORY, 15 GUILD_FORUM, 16 GUILD_MEDIA. Pick fields that match the type - extra fields are ignored by Discord.

Example: {guild_id:"…", name:"announcements", type:5, parent_id:"…"}

Returns: {id, name, type, parent_id, available_tags?, applied_tags?}. Forum/media tags include their Discord-assigned IDs, names, moderation and emoji fields.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Channel name (1-100 chars)
`nsfw`	No	Mark as NSFW
`type`	No	Discord channel type (omit for default GUILD_TEXT=0)
`topic`	No	Channel topic (text/forum/announcement only)
`bitrate`	No	Voice bitrate in bps (voice/stage)
`guild_id`	Yes	Target guild
`position`	No	Sort position
`parent_id`	No	Category to nest under
`rtc_region`	No	Voice region override (voice/stage)
`user_limit`	No	Voice user cap (0 = no limit)
`audit_reason`	No	Reason recorded in audit log (X-Audit-Log-Reason header)
`available_tags`	No	Forum tag set
`default_sort_order`	No	Forum sort order (0 LATEST_ACTIVITY, 1 CREATION_DATE)
`video_quality_mode`	No	1 AUTO, 2 FULL (voice/stage)
`rate_limit_per_user`	No	Slowmode in seconds (0-21600)
`default_forum_layout`	No	Forum layout (0 NOT_SET, 1 LIST_VIEW, 2 GALLERY_VIEW)
`permission_overwrites`	No	Permission overwrites to seed at creation
`default_reaction_emoji`	No	Forum default reaction (emoji_id OR emoji_name)
`default_auto_archive_duration`	No	Default thread auto-archive (60/1440/4320/10080 minutes)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.28.0Sep 15, 2026

removedInput schema / properties / available_tags / items / properties / emoji_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedInput schema / properties / available_tags / items / properties / emoji_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedInput schema / properties / available_tags / items / properties / emoji_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedInput schema / properties / available_tags / items / properties / emoji_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedInput schema / properties / default_reaction_emoji / properties / emoji_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedInput schema / properties / default_reaction_emoji / properties / emoji_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedInput schema / properties / default_reaction_emoji / properties / emoji_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedInput schema / properties / default_reaction_emoji / properties / emoji_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "id": {
-        "description": "Discord channel ID (snowflake)",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "parent_id": {
-        "anyOf": [
-          {
-            "description": "Discord channel ID (snowflake)",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "type": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "id",
-      "name",
-      "type",
-      "parent_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"
+      },
+      "available_tags": {
+        "description": "Complete forum/media tags, including IDs, names, moderation and emoji fields, when returned by Discord",
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "emoji_id": {
+              "anyOf": [
+                {
+                  "pattern": "^\\d{17,20}$",
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "emoji_name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "id": {
+              "pattern": "^\\d{17,20}$",
+              "type": "string"
+            },
+            "moderated": {
+              "type": "boolean"
+            },
+            "name": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "moderated",
+            "emoji_id",
+            "emoji_name"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "id": {
+        "description": "Discord channel ID (snowflake)",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "parent_id": {
+        "anyOf": [
+          {
+            "description": "Discord channel ID (snowflake)",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "type": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "type",
+      "parent_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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation is established. The description adds valuable context beyond that: 'extra fields are ignored by Discord' is a behavioral trait, and the return shape with optional tags is described. No contradiction with annotations.

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?

The description is well structured with bold headers, a usage list, an example, and return info. It is slightly long but each section earns its place; no filler. The front-loaded purpose and usage are especially effective.

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?

For a 19-parameter tool with a real output schema, this description covers the core decision factors: when to use, type mapping, field-behavior note, and return shape. It could mention required permissions (e.g., MANAGE_CHANNELS) or error conditions, but the schema and annotations already carry a lot of the burden.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by enumerating Discord channel type numeric values (0, 2, 4, 5, 13, 14, 15, 16) which the schema leaves as an open integer, and it adds a concrete example. This materially helps an agent choose the correct type and parameter combination.

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 'Create' and the resource 'a new channel in a guild', enumerating the channel types (text, voice, category, etc.). It explicitly distinguishes itself from thread-creation tools by naming the sibling alternatives, so an agent can immediately tell which tool to select.

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?

The description provides explicit 'When to use' scenarios (programmatic guild bootstrap, tier-based channel provisioning) and a dedicated 'When NOT to use' section that points to `messages_create_thread`, `channels_forum_create_thread`, or thread-specific tools. This gives unambiguous 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