Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_channel

Creates a channel in a Discord server with configurable type such as text, voice, or forum, plus name, topic, permissions, and category placement.

Instructions

Create a channel in a server. type: 0 text, 2 voice, 4 category, 5 announcement, 13 stage, 15 forum, 16 media. [POST /guilds/{guild_id}/channels]

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": {
      "guild_id": "<guild_id>",
      "name": "<name>"
    },
    "name": "create_guild_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
nsfwNo
typeNo
flagsNo
topicNo
reasonNoReason (shown in the audit log)
bitrateNo
guild_idYesServer (guild) ID
positionNo
parent_idNo
rtc_regionNo
user_limitNo
available_tagsNo
default_sort_orderNo
video_quality_modeNo
default_tag_settingNo
rate_limit_per_userNo
default_forum_layoutNo
permission_overwritesNo
default_reaction_emojiNo
default_auto_archive_durationNo
default_thread_rate_limit_per_userNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation, so the safety profile is covered. The description adds the underlying endpoint (POST /guilds/{guild_id}/channels) and the type mapping, but omits permission requirements, guild channel-creation rate limits, and whether a newly created channel starts with inherited or empty permission overwrites.

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?

Two compact sentences, front-loaded with the action, with no filler. The type enumeration duplicates the schema's own 'type' description, so it is slightly redundant rather than wasteful.

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

Completeness2/5

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

This is a 22-parameter mutation tool with 14% schema coverage and no output schema. The description accounts for roughly two of those parameters and gives no sense of what the response contains (a channel object) or how the optional fields interact, leaving an agent under-equipped to call it correctly.

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

Parameters2/5

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

Schema description coverage is only 14% across 22 parameters, so the description carries a heavy burden and largely fails it. It only restates the 'type' enumeration already present in the schema, leaving forum-specific fields (available_tags, default_sort_order, default_forum_layout), permission_overwrites, parent_id semantics, and position ordering unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Create a channel in a server') and enumerates the supported channel types, which clarifies scope well beyond the bare name. It stops short of distinguishing itself from siblings like create_thread or create_stage_instance, which also create channel-like objects.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, and no mention of the prerequisites that matter for a Discord channel creation call (MANAGE_CHANNELS permission, guild-level channel creation rate limits). The channel-type list implies which kinds can be made, but that is inference, not 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