Skip to main content
Glama
Oratorian

Discord MCP Server

by Oratorian
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Create Discord Channel

discord_create_channel

Create a new text, voice, category, or forum channel in a Discord server with customizable settings like topic, NSFW, bitrate, and forum layout.

Instructions

Create a new channel or category in a Discord server.

Args:

  • guild_id (string): Discord server/guild ID

  • name (string): Channel name

  • type ('text' | 'voice' | 'category' | 'forum'): Channel type (default: 'text')

  • topic (string, optional): Channel topic (text/forum channels only)

  • parent_id (string, optional): Category ID to create channel under (not for categories)

  • nsfw (boolean, optional): Whether the channel is NSFW (text/forum channels only)

  • bitrate (number, optional): Bitrate for voice channels (8000-384000)

  • user_limit (number, optional): User limit for voice channels (0 = unlimited)

  • default_reaction_emoji (string, optional): Default emoji for forum posts (emoji char or custom ID)

  • default_sort_order ('latest_activity' | 'creation_date', optional): Sort order for forum posts

  • default_forum_layout ('not_set' | 'list_view' | 'gallery_view', optional): Forum layout

  • available_tags (array, optional): Tags for forum posts (max 20)

    • name (string): Tag name (max 20 chars)

    • moderated (boolean, optional): Only mods can apply this tag

    • emoji_name (string, optional): Unicode emoji (e.g., '🎮')

    • emoji_id (string, optional): Custom emoji ID

Returns: The created channel's details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesChannel name
nsfwNoWhether the channel is NSFW (text/forum channels only)
typeNoChannel type: 'text', 'voice', 'category', or 'forum'text
topicNoChannel topic (text/forum channels only)
bitrateNoBitrate for voice channels (8000-384000)
guild_idYesDiscord server/guild ID (snowflake)
parent_idNoCategory ID to create channel under (not for categories)
user_limitNoUser limit for voice channels (0 = unlimited)
available_tagsNoAvailable tags for forum posts (max 20 tags)
default_sort_orderNoDefault sort order for forum posts
default_forum_layoutNoDefault layout for forum channel
default_reaction_emojiNoDefault reaction emoji for forum posts - use emoji character (e.g., '👍') or custom emoji ID

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

Annotations indicate a write operation (readOnlyHint false) and no destructive or idempotent behavior. The description adds no additional behavioral context beyond what the annotations provide, such as permission requirements, rate limits, or error conditions (e.g., duplicate names).

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 Args and Returns sections, making it easy to scan. However, it is verbose, listing all 12 parameters in detail when a shorter summary could suffice. Still, the structure earns a high score.

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 complexity of 12 parameters (2 required) and no output schema, the description thoroughly documents each parameter's purpose, type, constraints, and defaults. It covers all necessary details for an agent to correctly invoke the tool, leaving no obvious gaps.

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 coverage is 100%, meaning all parameters have schema descriptions. The description largely repeats this information with a structured Args list, adding marginal value like inline defaults and notes (e.g., 'not for categories' for parent_id). This provides some extra clarity but doesn't significantly surpass 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?

The description explicitly states 'Create a new channel or category in a Discord server', clearly identifying the verb (create) and resource (channel/category). This distinguishes it from sibling tools like discord_edit_channel and discord_delete_channel.

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 description provides no direct guidance on when to use this tool vs alternatives (e.g., when to create a category vs text channel, or when to use discord_edit_channel). The context is implied by the tool name and parameter types, but explicit usage instructions are missing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Oratorian/discord-node-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server