Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_bulk_delete_messages

Destructive

Bulk delete multiple recent Discord messages in one call. Preview with dry run first, then confirm actual deletion; messages older than 14 days are skipped.

Instructions

Permanently delete multiple recent messages in one call. IRREVERSIBLE. SAFE BY DEFAULT: dry_run is true unless explicitly set to false, so call it first to preview, then re-call with dry_run:false to actually delete. Discord only allows bulk-deleting messages younger than 14 days; older ones are skipped. Requires the Manage Messages permission. Returns the number deleted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of recent messages to delete (2–100).
dry_runNoIf true (default), only reports how many would be deleted without deleting. Set false to actually delete.
channel_idYesID (snowflake) of the channel or thread to delete messages from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed5 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / count / maximum
      Added value: +100
    • addedInput schema / properties / count / minimum
      Added value: +2
    • changedInput schema / properties / count / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / dry_run
      Added value: +{
+  "default": true,
+  "description": "If true (default), only reports how many would be deleted without deleting. Set false to actually delete.",
+  "type": "boolean"
+}
  3. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the channel or thread to delete messages from."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by disclosing irreversibility, the dry_run safe-by-default behavior, the 14-day Discord restriction, the required Manage Messages permission, and the return value. This gives an agent a complete behavioral picture before invoking a destructive operation.

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?

Four compact sentences, each carrying unique essential information: purpose, irreversibility, safe dry_run workflow, platform constraint, permission, and return value. No filler or repetition.

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

Completeness5/5

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

For a destructive multi-parameter tool with no output schema, this description is complete: it covers prerequisites, constraints, safety workflow, side effects, and outcome. An agent has everything needed to invoke it correctly and avoid accidental deletion.

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%, and the description mostly reinforces the dry_run behavior already documented in the schema. It adds a useful preview-then-delete workflow, but does not substantially redefine or extend the parameter meanings beyond what the schema already provides.

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 specific action, resource, and scope: 'Permanently delete multiple recent messages in one call.' This clearly distinguishes it from single-message deletion tools like discord_delete_message and other message operations.

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?

Provides clear contextual guidance: use for bulk deletion of recent messages, respect the 14-day Discord limit, and run with dry_run first to preview before actual deletion. It does not explicitly name the alternative single-delete tool or state 'do not use for one message,' but the context is strong enough for an agent to choose correctly.

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