Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_delete_channel

Permanently deletes a Discord channel or category after explicit confirmation, enabling agents to remove unwanted channels or categories from a server.

Instructions

Delete a channel or category. Requires confirm: true.

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>",
      "channelId": "<channelId>",
      "confirm": "<confirm>"
    },
    "name": "discord_delete_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
confirmYesMust be true. Deletion cannot be undone.
guildIdYesDiscord id (snowflake)
channelIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the critical trait that deletion cannot be undone. However, it omits other behavioral facts an agent needs: required permission level, whether deleting a category cascades to child channels, and whether messages/threads are lost.

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 sentences, front-loaded with the action and immediately followed by the hard requirement. The confirm statement partially duplicates the schema's own description, but it is short enough that the redundancy is cheap.

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?

For a destructive, unannotated, no-output-schema mutation tool with one undocumented parameter, the definition covers the minimum (what it does, irreversibility, confirm flag) but leaves permission requirements and cascade side effects unexplained.

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 50% — guildId, channelId, and confirm are documented in the schema, while 'reason' is not. The description reinforces the confirm semantics and irreversibility but adds nothing about the audit-log 'reason' parameter, so it does not compensate for the gap.

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?

States a specific verb and resource ('Delete a channel or category'), which cleanly separates it from the create/edit/info channel siblings. It does not explicitly name or contrast with an alternative, so it stops short of a 5.

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?

The description conveys that this is a destructive action requiring 'confirm: true', which implies when it applies, but gives no explicit when-to-use guidance, no alternatives (e.g. archive thread, edit channel), and no prerequisites such as required permissions (MANAGE_CHANNELS).

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