discord_delete_channel
Delete a Discord channel by its ID, optionally including a reason for the action.
Instructions
Deletes a Discord channel with an optional reason
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | ||
| channelId | Yes |
Delete a Discord channel by its ID, optionally including a reason for the action.
Deletes a Discord channel with an optional reason
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | ||
| channelId | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must fully convey behavior. It only mentions deletion with an optional reason, but does not disclose permanence, permissions, or side effects like message loss.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no wasted words. However, it could be expanded without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's destructive nature, lack of annotations, and no output schema, the description is too minimal. It does not cover important context like reversibility or success confirmation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description should compensate. It only adds that 'reason' is optional, but does not explain 'channelId' or provide format constraints. Minimal added value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'deletes' and the resource 'Discord channel', with an optional reason. It distinguishes from sibling tools that delete other types of content.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like discord_delete_category or discord_delete_forum_post. The description lacks any context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/danushkumar-v/mcp-discord'
If you have feedback or need assistance with the MCP directory API, please join our Discord server