Skip to main content
Glama

Bulk delete messages (admin)

discord_admin_purge_messages
Destructive

Delete up to 100 recent messages in a Discord channel or thread, optionally filtering by author, bots, or text; messages older than 14 days are skipped.

Instructions

Delete up to 100 recent messages in a channel or thread, optionally only from one user, only bots, or containing some text. Discord only bulk-deletes messages under 14 days old; older ones are skipped. Cannot be undone; confirm with the user first.

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>",
      "count": "<count>"
    },
    "name": "discord_admin_purge_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesHow many recent messages to look at
reasonNoReason, recorded in Discord's audit log
containsNo
author_idNoOnly this user's messages
bots_onlyNo
channel_idYesChannel, thread or post

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is known; the description goes further by disclosing the Discord-side 14-day cutoff, that older messages are silently skipped, that the action is irreversible, and that confirmation is expected. It does not state required permissions (Manage Messages) or whether the result reports a deleted-vs-skipped count, which are the remaining 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?

Three sentences, front-loaded with the action and scope, then constraints, then the safety warning. No filler or restatement of the title.

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, six-parameter tool with no output schema, the description covers the critical operational facts an agent needs: the 100-message cap, the 14-day skip behavior, irreversibility, and user confirmation. Missing only permission prerequisites and what the return value reports about skipped versus deleted messages.

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

Parameters4/5

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

Schema coverage is 67% and the description maps meaning onto the undocumented filters: 'only from one user' (author_id), 'only bots' (bots_only), 'containing some text' (contains), and clarifies count as how many recent messages are examined rather than a guaranteed deletion total. The reason parameter's audit-log purpose is left entirely to the schema.

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?

States a concrete verb and resource ('Delete up to 100 recent messages in a channel or thread') and enumerates the three filter modes (one user, bots only, matching text), which lets an agent distinguish this bulk operation from single-message or read tools in the sibling list without opening the schema.

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?

Gives clear triggering context: use it for bulk cleanup of recent messages, and it explicitly says to confirm with the user first before invoking. It falls short of naming an alternative for single-message deletion or for messages older than 14 days, so the agent must infer what to do in those cases.

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