Skip to main content
Glama

discord_delete_channel

Remove a Discord channel by specifying its ID, with optional reason for audit logs.

Instructions

Delete a channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
reasonNo

Implementation Reference

  • The handler logic for the 'discord_delete_channel' tool, which fetches the Discord channel and deletes it.
    case "discord_delete_channel": {
      const channel = await discord.channels.fetch(args.channel_id as string);
      if (!channel) throw new Error("Channel not found.");
      const channelName = "name" in channel ? channel.name : channel.id;
      await channel.delete(args.reason as string | undefined);
      return { content: [{ type: "text", text: `✅ Channel #${channelName} deleted.` }] };
    }
  • The tool definition and input schema for 'discord_delete_channel'.
    {
      name: "discord_delete_channel",
      description: "Delete a channel.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          reason: { type: "string" },
        },
        required: ["channel_id"],
      },
    },
Behavior1/5

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

With no annotations provided, the description carries full burden but fails to disclose behavioral traits. It doesn't indicate that this is a destructive operation, specify required permissions, mention irreversible effects, or describe error conditions (e.g., invalid channel_id). The single verb 'Delete' implies mutation but lacks critical safety context.

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 is extremely concise with zero wasted words—a single sentence that directly states the action. However, this brevity comes at the cost of completeness, making it under-specified rather than efficiently informative.

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

Completeness1/5

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

For a destructive tool with no annotations, 0% schema coverage, and no output schema, the description is completely inadequate. It lacks purpose differentiation, usage context, behavioral warnings, parameter explanations, and expected outcomes, failing to compensate for missing structured data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning parameters 'channel_id' and 'reason' are undocumented in the schema. The description adds no meaning about these parameters—it doesn't explain what 'channel_id' represents, its format, or what 'reason' is used for (e.g., audit logs). This leaves both parameters semantically opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a channel' is a tautology that restates the tool name 'discord_delete_channel' without adding specificity. It doesn't clarify what type of channel (text, voice, forum, etc.) or distinguish it from sibling tools like 'discord_delete_forum_post' or 'discord_delete_webhook' that also delete Discord resources.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., permissions), consequences, or relationships with sibling tools like 'discord_edit_channel' for modifications or 'discord_list_channels' for viewing channels before deletion.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server