Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_channel

Destructive

Deletes a Discord channel, category, thread or DM/group DM to remove unwanted spaces or close conversations. Provide the channel ID to permanently delete it or leave the group.

Instructions

Delete a server channel / category, close a DM, leave a group DM, or delete a thread. [DELETE /channels/{channel_id}]

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>"
    },
    "name": "delete_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
silentNosilent
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the danger profile is structured data. The description does add scope beyond that by clarifying that "delete" here means different things per channel type (close for DMs, leave for group DMs), which prevents a wrong mental model. It says nothing about irreversibility, required permissions, or that deletion removes associated messages/threads.

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 compact sentences, front-loaded with the verb and scope variants; nothing is padded. The trailing bracketed HTTP endpoint is mildly redundant but serves as a useful mapping hint.

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?

With three simple parameters, full schema coverage, and a destructive annotation, the definition covers the operation modes adequately. What is missing for a destructive mutation is the operational context: permission requirements, whether deletion is reversible, and what happens to a channel's contents.

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 description coverage is 100%, so channel_id, reason, and silent are all documented in the schema itself, and the baseline of 3 applies. The description adds no extra meaning for any parameter — notably it does not explain that `silent` suppresses the usual system message or that absence of `reason` leaves the audit log entry empty.

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?

The description names a specific verb (delete) and resource (channel), then enumerates every scope the tool actually covers: server channel/category, DM close, group DM leave, and thread deletion. That enumeration lets an agent distinguish this from siblings like delete_channel_permission or delete_channel_integration, which target sub-resources rather than the channel itself.

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?

Usage is only implied: by saying it can "close a DM" or "leave a group DM," the description tells the agent to reach for this tool in those situations rather than a separate DM tool. There is no explicit when-not-to-use guidance, no prerequisites (e.g., required permissions), and no named alternative for related operations.

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