Skip to main content
Glama

Delete channel (admin)

discord_admin_delete_channel
Destructive

Permanently delete a Discord channel, forum with all posts, or empty category. Requires the channel's exact name to confirm, so verify with the user before irreversible removal.

Instructions

Permanently delete a channel, forum (with all its posts) or empty category. Cannot be undone. confirm_name must equal the channel's exact name. Confirm with the user first.

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": {
      "channel_id": "<channel_id>",
      "confirm_name": "<confirm_name>"
    },
    "name": "discord_admin_delete_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason, recorded in Discord's audit log
channel_idYesChannel ID
confirm_nameYesThe channel's exact current name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds real context beyond them: irreversibility ('Cannot be undone'), the collateral effect on forum posts, the empty-category restriction, and the exact-match guardrail on confirm_name that prevents accidents. It also notes the reason field feeds Discord's audit log.

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?

Four short sentences, front-loaded with the destructive scope, then the permanence warning, then the guardrail, then the user-confirmation step. No filler and no repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 3-parameter destructive mutation with no output schema, the description covers irreversibility, scope, preconditions, and safety confirmation. It omits required permission level and what happens to existing threads/messages inside a deleted channel, which would matter for an admin tool.

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 100%, so the baseline is 3. The description restates the confirm_name rule (already documented in the schema property) and says nothing about the optional reason parameter beyond what the schema already explains, so it adds little new parameter meaning.

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?

States a specific verb (permanently delete) and resource (channel, forum, empty category), and scopes the destruction ('with all its posts') in a way that separates it from discord_admin_edit_channel and discord_admin_clone_channel. An agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear precondition ('empty category' only) and an explicit user-facing rule ('Confirm with the user first'), which shapes when the tool may be invoked. It stops short of naming a preferred alternative for non-empty categories or pointing at sibling tools, so it is strong context without full when-not/alternatives coverage.

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