Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

bulk_delete_messages

Destructive

Delete 2–100 Discord messages younger than 14 days in a channel in one request. Requires Manage Messages permission; use purge_my_messages for your own messages.

Instructions

Bulk-delete 2-100 messages younger than 14 days (needs Manage Messages; bots only on most servers). For your own messages use purge_my_messages. [POST /channels/{channel_id}/messages/bulk-delete]

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": {
      "channel_id": "<channel_id>",
      "messages": "<messages>"
    },
    "name": "bulk_delete_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
messagesYesmessages
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the destructiveHint/openWorldHint annotations by disclosing the hard limits (2-100 messages, under 14 days old) and the required Manage Messages permission. It does not say whether deletion is reversible or how partial failures are handled, which is the remaining gap for a destructive bulk operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the operation and its constraints, followed by the sibling disambiguation and endpoint in brackets. The bracketed route is arguably redundant for an agent, but everything else 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?

For a destructive bulk tool with full schema coverage and no output schema, the definition covers limits, permissions, and alternatives adequately. It stops short of describing atomicity or the response on partial failure, which would matter for a batch delete.

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 coverage is 100%, so channel_id, messages, and reason are already documented structurally. The description adds the useful constraint that the messages array must contain 2-100 items all under 14 days old, but adds nothing about reason or channel_id semantics; baseline 3 applies.

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?

Names a specific verb and resource (bulk-delete messages) and pins the operation to a channel-scoped endpoint. It immediately separates itself from the sibling purge_my_messages, which covers the self-owned-message case.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this tool for bulk channel deletion, but use purge_my_messages for your own messages. It also states the environment precondition (bots only on most servers), so the agent knows when the call is viable at all.

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