Skip to main content
Glama
Sign In
Discord Server Setup MCP

Discord Server Setup MCP

by cj-vana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_channel

Delete a Discord channel permanently. Provide the channel ID to remove it; this action cannot be undone.

Instructions

Deletes a channel from a Discord server. This action cannot be undone.

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

Input Schema

NameRequiredDescriptionDefault
guildIdNoGuild ID or name. Defaults to the currently selected guild.
channelIdYesID of the channel to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • addedInput schema / properties / channelId / description
      Added value: +"ID of the channel to delete"
    • addedInput schema / properties / guildId / description
      Added value: +"Guild ID or name. Defaults to the currently selected guild."
  2. First observedv2.0.0

TDQS

A3.8/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 of behavioral disclosure. It correctly states the action is irreversible, but it does not mention side effects on messages, permission requirements, or whether the deletion is immediate or eventual.

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?

The description consists of two concise sentences with no unnecessary words. It front-loads the primary action and immediately follows with a critical caveat about irreversibility.

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?

Given the absence of an output schema, the description adequately covers the main behavior (deletion) and a key constraint (irreversibility). It could be more complete by mentioning permission requirements or what happens to messages, but overall it serves its purpose.

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?

The schema already provides full descriptions for both parameters (guildId, channelId). The tool description adds no additional information about parameter semantics beyond what the schema offers, meeting the baseline expectation.

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 clearly states that the tool deletes a channel from a Discord server, using a specific verb and resource. It distinguishes itself from sibling tools like create_channel or edit_channel.

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 implies that this is a destructive action by noting 'cannot be undone', but it does not explicitly state when to use this tool versus alternative actions (e.g., archiving) or mention prerequisites like having manage channels permission.

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