Skip to main content
Glama
Sign In
Capes

Capes

by Dipeshpal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

discord_create_channel

Create a Discord channel in a server; requires Manage Channels. Choose text, voice, category, announcement, stage, or forum type and set topic, privacy, NSFW, slowmode, or parent category.

Instructions

Create a channel in a server. Needs 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": {
      "guild_id": "<guild_id>",
      "name": "<name>"
    },
    "name": "discord_create_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
nsfwNo
typeNoDefault text
topicNo
privateNoHide from @everyone (the bot keeps access). Use discord_set_channel_permission to let roles in.
guild_idYesServer (guild) ID
parent_idNoCategory ID to put the channel under
slowmode_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds the important permission requirement 'Needs Manage Channels,' which is not captured elsewhere. However, it does not disclose other behavioral traits such as error conditions, rate limits, or what happens to existing channels.

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?

Two short sentences, front-loaded with purpose and then the permission requirement. Every word earns its place, with no redundancy.

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 mutation tool with 8 parameters and only 50% schema coverage, the description is too sparse. It omits usage guidance and parameter semantics, leaving the agent with gaps that structured fields only partially fill. Annotations help with safety, but the overall definition is incomplete.

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 description mentions no parameters at all, despite there being 8 parameters and only 50% schema description coverage. Key parameters like name, nsfw, topic, and slowmode_seconds lack schema descriptions, and the description does nothing to compensate.

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 channel in a server.' This clearly distinguishes it from read/update/delete channel siblings, though it does not explicitly differentiate from other create tools like discord_create_thread. Still, the purpose is immediately clear.

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 only guidance is 'Needs Manage Channels,' which is a permission prerequisite, not when-to-use versus alternatives. There is no indication of when to choose this over discord_edit_channel or other creation tools, nor any exclusion criteria.

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