Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_delete_channel

Destructive

Permanently delete a Discord channel and all its messages. Preview with dry_run first, then re-call with dry_run:false to confirm deletion. Requires Manage Channels permission.

Instructions

Permanently delete a channel and all of its messages. IRREVERSIBLE. SAFE BY DEFAULT: dry_run is true unless explicitly set to false, so call it first to preview, then re-call with dry_run:false to actually delete. Requires the Manage Channels permission. An optional reason is recorded in the audit log.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoOptional reason recorded in the server audit log.
dry_runNoIf true (default), only reports which channel would be deleted without deleting it. Set false to actually delete.
channel_idYesID (snowflake) of the channel to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / dry_run
      Added value: +{
+  "default": true,
+  "description": "If true (default), only reports which channel would be deleted without deleting it. Set false to actually delete.",
+  "type": "boolean"
+}
  3. Changed2 schema fields changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the channel to delete."
    • addedInput schema / properties / reason / description
      Added value: +"Optional reason recorded in the server audit log."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.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 and readOnlyHint=false, and the description builds on this by specifying what is destroyed (the channel and all its messages), labeling the operation IRREVERSIBLE, describing the dry_run safeguard, and disclosing the audit-log side effect and permission requirement. It contradicts none of the annotations.

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?

Three sentences with no wasted words: the destructive scope and irreversibility are front-loaded, followed immediately by the dry_run safeguard, then permission and audit-log context. Every sentence earns its place.

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?

With no output schema, the description covers what the tool does, what it destroys, how to invoke it safely, who may use it, and what side effects it causes. The only gap is the return format of the dry-run preview and of the actual deletion, which is minor for a simple mutation 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 description coverage is 100%, so the schema fully documents channel_id, dry_run, and reason. The description reinforces dry_run's safety role and the audit-log behavior but adds no new per-parameter meaning beyond the schema, keeping this at the high-coverage baseline of 3.

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 opens with 'Permanently delete a channel and all of its messages,' a specific verb and resource with explicit scope. The phrase 'all of its messages' disambiguates it from siblings like discord_delete_message and discord_bulk_delete_messages, which operate on messages 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 Guidelines4/5

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

The description gives an explicit two-step workflow: 'call it first to preview, then re-call with dry_run:false to actually delete,' and states the prerequisite 'Requires the Manage Channels permission.' It does not explicitly name alternatives or say when not to use it, so it falls just short of full routing guidance.

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