discord-mcp

discord_bulk_delete_messages

Destructive

Deletes 2 to 100 messages from a Discord guild channel in one request; the operation fails if any message is older than 14 days or any ID is duplicated.

Instructions

Delete 2 to 100 messages from a guild channel in one request. The whole request fails if any message is older than 14 days or any message ID is duplicated. To delete a single message instead use discord_delete_message. Bot permissions it may need: View Channel, Manage Messages. Destructive: the user is asked to approve the exact change before it runs.

Input Schema

Name	Required	Description
`reason`	No	Audit log reason sent in the X-Audit-Log-Reason header (up to 512 characters)
`channel_id`	Yes	ID of the channel containing the messages to delete
`message_ids`	Yes	Array of 2 to 100 unique message IDs younger than 14 days to delete

Output Schema

Name	Required	Description
`deleted`	Yes
`channel_id`	Yes	Discord snowflake ID as a numeric string
`message_ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.1.2Nov 4, 2026

addedInput schema / properties / channel_id / description

Added value: +"ID of the channel containing the messages to delete"

addedInput schema / properties / message_ids / description

Added value: +"Array of 2 to 100 unique message IDs younger than 14 days to delete"

addedInput schema / properties / message_ids / items / description
```
Added value: +"Message snowflake ID to delete"
```

changedInput schema / properties / reason / description

Previous value: -"Audit log reason"New value: +"Audit log reason sent in the X-Audit-Log-Reason header (up to 512 characters)"

addedOutput schema / properties / channel_id / description

Added value: +"Discord snowflake ID as a numeric string"

addedOutput schema / properties / message_ids / items / description
```
Added value: +"Discord snowflake ID as a numeric string"
```

First observedv0.1.0Nov 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, so the safety profile is known, but the description adds real substance beyond them: atomic all-or-nothing failure semantics, the 14-day age ceiling, duplicate-ID rejection, and the specific bot permissions (View Channel, Manage Messages). The approval-before-execution note reinforces the destructive hint with concrete behavior.

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?

Four tight sentences, front-loaded with the scope and immediately followed by the sibling alternative and failure modes. The final 'Destructive: the user is asked to approve' sentence partially restates destructiveHint=true, but the rest earns its place.

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?

With an output schema present, return values need no explanation, and the description covers scope, limits, failure modes, permissions, and the alternative tool. Nothing an agent needs in order to decide or call correctly is missing for a destructive bulk operation.

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 schema already documents the 2-100 bounds, uniqueness, and 14-day age requirement per field. The description adds the consequence of violating those constraints (the whole request fails) but says nothing about the 'reason' audit-log parameter. Baseline 3 is appropriate since the schema carries the parameter detail.

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 verb and resource with scope: 'Delete 2 to 100 messages from a guild channel in one request.' It also names the sibling discord_delete_message as the single-message alternative, so an agent can distinguish the two without opening either schema.

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?

Gives explicit routing: use this for bulk, use discord_delete_message for a single message. It also states the conditions under which the call is rejected (any message older than 14 days, duplicated IDs), which is exactly the pre-call check an agent needs.

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