Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_create_channel

Create a Discord channel or category, including text, voice, forum, or stage, with optional topic, NSFW, slowmode, and parent settings. Requires Manage Channels.

Instructions

Create a channel or category. Requires Manage 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": {
      "guildId": "<guildId>",
      "name": "<name>"
    },
    "name": "discord_create_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
nsfwNo
typeNoGUILD_TEXT
topicNo
reasonNo
guildIdYesDiscord id (snowflake)
parentIdNoCategory to place the channel in
positionNo
slowmodeSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; it does add one genuinely useful behavioral fact, the Manage Channels permission requirement, which is not in the schema. Beyond that it says nothing about reversibility, side effects of creation, ordering behavior for position, or how parentId interacts with the type field, leaving the mutation semantics largely undisclosed.

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 short, front-loaded sentences with no filler; the action comes first and the constraint second. It is efficient, though its brevity reflects under-specification addressed in other dimensions rather than a model of completeness.

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?

For a 9-parameter create/mutation tool with no annotations, no output schema, and low schema coverage, the description is too thin. An agent gets the action and one permission rule but no insight into the type enum's meaning, parent/position semantics, or the shape of the created object.

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 22% of 9 parameters, so the description must compensate — and it does not. The phrase 'channel or category' hints at the type enum, but nothing explains the seven enum members, how parentId must point at a GUILD_CATEGORY, or what position and slowmodeSeconds do.

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 names a specific verb and resource ('Create a channel or category'), which clearly separates it from siblings like discord_edit_channel, discord_delete_channel, and discord_create_thread without needing the schema. It stops short of explicitly naming those alternatives, but the action itself is unambiguous.

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?

It states a prerequisite ('Requires Manage Channels'), which is useful gating context, and the create-verb implies use when a new channel or category is needed. However, there is no explicit guidance on when to use this versus discord_create_thread, discord_edit_channel, or discord_set_channel_position, and no stated exclusions.

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