Skip to main content
Glama
cj-vana

Discord Server Setup MCP

by cj-vana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_channel

Create text, voice, announcement, stage, or forum channels in a Discord server with configuration for name, type, topic, permissions, and more.

Instructions

Creates a new channel in a Discord server. Supports text, voice, announcement, stage, and forum channels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the channel (1-100 characters)
nsfwNoWhether the channel is age-restricted
typeNoChannel type (default: text)text
topicNoChannel topic (text channels, max 1024 chars)
bitrateNoBitrate for voice channels (8000-384000)
guildIdNoGuild ID or name. Defaults to the currently selected guild.
positionNoPosition in the channel list
slowmodeNoSlowmode in seconds (0-21600)
userLimitNoUser limit for voice channels (0-99, 0 = unlimited)
categoryIdNoID of the category to place this channel in
permissionOverwritesNoPermission overwrites for roles/users.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv2.0.1
    • addedInput schema / properties / bitrate / description
      Added value: +"Bitrate for voice channels (8000-384000)"
    • addedInput schema / properties / categoryId / description
      Added value: +"ID of the category to place this channel in"
    • addedInput schema / properties / guildId / description
      Added value: +"Guild ID or name. Defaults to the currently selected guild."
    • addedInput schema / properties / name / description
      Added value: +"Name of the channel (1-100 characters)"
    • addedInput schema / properties / nsfw / description
      Added value: +"Whether the channel is age-restricted"
    • addedInput schema / properties / permissionOverwrites / description
      Added value: +"Permission overwrites for roles/users."
    • changedInput schema / properties / permissionOverwrites / items / properties / allow / description
      Previous value: -"Permissions to allow"New value: +"Permission names to allow (SCREAMING_SNAKE_CASE)"
    • changedInput schema / properties / permissionOverwrites / items / properties / deny / description
      Previous value: -"Permissions to deny"New value: +"Permission names to deny (SCREAMING_SNAKE_CASE)"
    • changedInput schema / properties / permissionOverwrites / items / properties / id / description
      Previous value: -"Role ID or user ID"New value: +"Role ID or user ID this overwrite applies to"
    • changedInput schema / properties / permissionOverwrites / items / properties / type / description
      Previous value: -"Whether this is a role or user override"New value: +"Whether id refers to a role or a member"
    • addedInput schema / properties / position / description
      Added value: +"Position in the channel list"
    • addedInput schema / properties / slowmode / description
      Added value: +"Slowmode in seconds (0-21600)"
    • addedInput schema / properties / topic / description
      Added value: +"Channel topic (text channels, max 1024 chars)"
    • addedInput schema / properties / type / description
      Added value: +"Channel type (default: text)"
    • addedInput schema / properties / userLimit / description
      Added value: +"User limit for voice channels (0-99, 0 = unlimited)"
  2. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only states 'creates' without disclosing side effects, required permissions, or whether the operation is reversible. Behavior beyond creation is opaque.

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 concise at two sentences without waste. However, it could be slightly more informative without losing conciseness.

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?

Given the complexity (11 parameters, no output schema), the description is insufficient. It does not explain return values, error conditions, or any broader context needed for proper invocation.

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%, so parameters are well-documented in the schema. The description adds no additional meaning beyond listing channel types already present in the schema enum.

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 clearly states it creates a new channel and lists supported types, making the purpose evident. However, it does not differentiate from sibling tools like create_category or create_role, which could be confused.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or context for usage. The description lacks any indication of when to choose this over other creation tools.

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