discord-server-mcp

create_channel

Create a Discord text, announcement, forum, media, voice, or stage channel, set its category, topic, and permission overrides, and preview changes with a dry run.

Instructions

Create a text, announcement, forum, media, voice or stage channel. Inside a category it takes the category's permissions unless overrides are given. Permission names: CreateInstantInvite, KickMembers, BanMembers, Administrator, ManageChannels, ManageGuild, AddReactions, ViewAuditLog, PrioritySpeaker, Stream, ViewChannel, SendMessages, SendTTSMessages, ManageMessages, EmbedLinks, AttachFiles, ReadMessageHistory, MentionEveryone, UseExternalEmojis, ViewGuildInsights, Connect, Speak, MuteMembers, DeafenMembers, MoveMembers, UseVAD, ChangeNickname, ManageNicknames, ManageRoles, ManageWebhooks, ManageGuildExpressions, UseApplicationCommands, RequestToSpeak, ManageEvents, ManageThreads, CreatePublicThreads, CreatePrivateThreads, UseExternalStickers, SendMessagesInThreads, UseEmbeddedActivities, ModerateMembers, ViewCreatorMonetizationAnalytics, UseSoundboard, CreateGuildExpressions, CreateEvents, UseExternalSounds, SendVoiceMessages, SendPolls, UseExternalApps, PinMessages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_channel"
  }
}

Input Schema

Name	Required	Description	Default
`bot`	No	Use this bot (name or id) instead of choosing automatically
`name`	Yes
`nsfw`	No
`type`	No		text
`topic`	No	Topic, or the guidelines of a forum
`reason`	No	Reason shown in the server's audit log
`server`	No	Server name or id. Optional when the bot is in one server or DISCORD_GUILD_ID is set.
`bitrate`	No	Voice: bits per second, e.g. 64000
`dry_run`	No	Show the requests that would be made without changing anything
`private`	No	Hide from @everyone (add overrides to let roles see it)
`category`	No	Category name or id
`position`	No
`overrides`	No
`forum_sort`	No
`forum_tags`	No
`user_limit`	No	Voice: 0 = no limit
`forum_layout`	No
`slowmode_seconds`	No
`forum_default_reaction`	No	Forum: unicode emoji added under every post

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description must carry the rest, and it does add real behavior: permission inheritance from a parent category unless overrides are supplied, and the semantics of the private flag ('hide from @everyone (add overrides to let roles see it)'). It omits prerequisites (does the bot need Manage Channels?) and any failure/return behavior, keeping it below a 5.

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 core capability and the category-inheritance caveat are front-loaded in two short sentences, and the long permission enumeration follows as reference data that is not available anywhere else. The permission list is dense and dominates the description, but it earns its space as an enum of valid override values.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter mutation tool with only readOnlyHint=false and no output schema, the description covers the two trickiest concepts (inheritance and permission names) but says nothing about required bot permissions, name-collision behavior, or what the call returns. Many parameters are handled by the schema, so it is adequate but not fully self-sufficient.

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?

With 19 parameters at 53% schema description coverage, the description plugs the single largest gap: the overrides allow/deny arrays are typed only as strings in the schema, and the 50-entry permission name list is the only place valid values are enumerated. It also clarifies private and category semantics beyond their schema text, though bitrate, forum_*, slowmode and position still rely solely on the schema.

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?

Opens with a specific verb plus resource and enumerates the exact channel types it can create (text, announcement, forum, media, voice, stage), which immediately separates it from siblings such as create_category or create_thread. An agent knows precisely what object is produced without opening the schema.

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 clause about inheriting a category's permissions gives situational context for the category parameter, but there is no explicit when-to-use guidance and no routing to alternatives (e.g. create_category vs create_channel, or edit_channel when the channel already exists). Usage is implied rather than stated.

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