Skip to main content
Glama

discord_delete_message

Delete specific messages from Discord channels using channel and message IDs. Remove unwanted content or correct errors in your server.

Instructions

Delete a specific message from a channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
message_idYes
reasonNo

Implementation Reference

  • The handler implementation for discord_delete_message that fetches the channel, retrieves the message, and deletes it.
    case "discord_delete_message": {
      const channel = await getTextChannel(args.channel_id as string);
      const msg = await channel.messages.fetch(args.message_id as string);
      await msg.delete();
      return { content: [{ type: "text", text: `✅ Message ${args.message_id} deleted.` }] };
    }
  • The MCP schema definition for discord_delete_message, specifying input requirements.
    {
      name: "discord_delete_message",
      description: "Delete a specific message from a channel.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          message_id: { type: "string" },
          reason: { type: "string" },
        },
        required: ["channel_id", "message_id"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the destructive action ('Delete') but doesn't mention permission requirements, whether deletions are permanent/reversible, rate limits, or what happens on success/failure. This leaves significant gaps for a mutation tool.

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 a single, focused sentence with zero wasted words. It's front-loaded with the core action and target, making it immediately scannable and efficient.

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

Completeness2/5

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

For a destructive mutation tool with 3 parameters (0% schema coverage) and no annotations or output schema, the description is inadequate. It doesn't address permission requirements, error conditions, return values, or how it differs from similar deletion tools. The agent would need to guess critical implementation details.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all three parameters. It mentions 'a specific message' (hinting at message_id) and 'from a channel' (hinting at channel_id), but doesn't explain the 'reason' parameter or provide format/validation details. The description adds minimal value beyond what's inferable from parameter names.

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

Purpose4/5

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

The description clearly states the action ('Delete') and target ('a specific message from a channel'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'discord_bulk_delete_messages', but the specificity of 'a specific message' provides some implicit distinction.

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

Usage Guidelines2/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 like 'discord_bulk_delete_messages' or 'discord_edit_message' for content removal. The description lacks context about prerequisites, permissions needed, or typical use cases for message 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