MCP Discord Bot Server

discord_create_text_channel

Create a new text channel in a Discord server by providing the guild ID and channel name. Returns the created channel details.

Instructions

Create a new text channel in a Discord guild (server).

Args:
    guild_id: The ID of the Discord guild.
    name: The name for the new text channel.

Returns:
    JSON object with the created channel details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	The name for the new text channel. Required.
`guild_id`	Yes	The ID of the Discord guild (server) to create the channel in. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It confirms this is a mutation and that a JSON object of created channel details is returned, but omits permission requirements, Discord's channel-creation rate limits, and default/derived behavior for the new channel — significant gaps for a write operation.

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 opening sentence is front-loaded and tight. The Args/Returns block largely duplicates schema and output-schema content but stays short, so the cost is minor.

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?

Because an output schema exists, the description need not explain the return value, and the two required params are schema-documented. However, for a mutation tool with zero annotations, the missing permission and failure-mode context leaves the definition only minimally complete.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already fully documented in the schema, and the description merely restates them. No syntax, format, or constraint detail is added beyond what the schema provides, so the baseline of 3 applies.

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 new text channel in a Discord guild'), which the agent cannot confuse with read/message siblings like discord_list_channels or discord_send_message. It stops short of explicitly naming or contrasting any sibling tool, so it is clear but not sibling-differentiated.

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, no mention of prerequisites (e.g. requiring Manage Channels permission), and no note about what happens if a channel with the same name already exists. The agent gets a purpose but no selection or precondition context.

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

Deploy Server