MCP-Discord

discord_create_voice_channel

Create a new voice channel in a Discord server, optionally specifying a parent category.

Instructions

Creates a new voice channel in a Discord server with an optional parent category

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": {
      "guildId": "<guildId>",
      "channelName": "<channelName>"
    },
    "name": "discord_create_voice_channel"
  }
}

Input Schema

Name	Required	Description
`reason`	No
`guildId`	Yes
`userLimit`	No	Maximum number of users allowed (0 for unlimited)
`categoryId`	No	Parent category ID to place the channel under
`channelName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.0Sep 7, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing side effects. It only states the creation action but does not mention required permissions (e.g., 'manage channels'), potential failures, or any other behavioral implications beyond the obvious creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that efficiently conveys the tool's purpose and key optional aspect. No redundant information or filler is present.

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?

The description is adequate for a simple creation tool but lacks context about expected input format, possible constraints (e.g., name length), and return/output information. However, since no output schema is required and the operation is straightforward, the missing context is minor.

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?

The schema covers 5 parameters, but only userLimit and categoryId have descriptions (40% coverage). The description does not compensate: it does not explain guildId, channelName, or reason. While some are self-evident from names, the lack of explicit semantic context for half the parameters leaves ambiguity.

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 clearly states the tool's verb ('Creates'), resource ('a new voice channel'), and scope ('in a Discord server'), with an optional parent category. It is easily distinguishable from sibling tools like discord_create_text_channel and discord_create_forum_channel.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It does not mention scenarios where voice channels are needed or contrast with other channel creation tools, leaving the agent to infer usage from the tool name alone.

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

Deploy Server