Skip to main content
Glama

discord_bulk_delete_messages

Delete multiple Discord messages at once (2-100 messages, under 14 days old) to manage channels and remove unwanted content efficiently.

Instructions

Delete multiple messages at once (2–100, messages must be less than 14 days old).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
countYesNumber of recent messages to delete (2–100).

Implementation Reference

  • The handler logic for "discord_bulk_delete_messages" which fetches the text channel and performs the bulk deletion using discord.js.
    case "discord_bulk_delete_messages": {
      const channel = await getTextChannel(args.channel_id as string);
      const count = Math.min(Math.max(Number(args.count ?? 2), 2), 100);
      const deleted = await channel.bulkDelete(count, true);
      return { content: [{ type: "text", text: `✅ Deleted ${deleted.size} messages in #${channel.name}.` }] };
    }
  • The schema definition for "discord_bulk_delete_messages" tool, specifying input arguments and constraints.
      name: "discord_bulk_delete_messages",
      description: "Delete multiple messages at once (2–100, messages must be less than 14 days old).",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          count: { type: "number", description: "Number of recent messages to delete (2–100)." },
        },
        required: ["channel_id", "count"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the deletion action and constraints but lacks critical details: it doesn't specify whether this is a destructive operation (implied but not stated), what permissions are required, whether deletions are reversible, how messages are selected (e.g., most recent), or what happens on failure. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that front-loads the core action and includes all essential constraints without redundancy. Every word earns its place, making it easy to parse quickly while conveying key information.

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?

Given the tool's complexity (destructive batch operation), lack of annotations, and no output schema, the description is minimally adequate but incomplete. It covers the basic action and constraints but misses important context like permissions, error handling, selection method (e.g., most recent messages), and response format. For a mutation tool with significant impact, more detail would be helpful.

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 50% (only 'count' has a description), so the description must compensate. It adds value by explaining the 'count' parameter's range (2–100) and implying message selection criteria, but doesn't clarify 'channel_id' semantics or how messages are chosen (e.g., recent messages). The description partially compensates but doesn't fully address the coverage gap for both parameters.

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 the specific action ('Delete multiple messages at once') with precise resource scope ('messages'), and distinguishes it from the sibling tool 'discord_delete_message' which handles single messages. It provides explicit quantitative constraints (2–100 messages, less than 14 days old) that further clarify its purpose.

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 implicitly provides usage guidance by specifying the message count range (2–100) and age constraint (less than 14 days old), indicating when this tool is appropriate. However, it doesn't explicitly mention when to use this versus 'discord_delete_message' for single deletions or other message management tools, nor does it discuss prerequisites like permissions or channel context.

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