Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

purge_my_messages

Destructive

Deletes your recent Discord messages in a channel or DM, optionally only those containing specific text, with dry-run preview and rate-limit-aware pacing.

Instructions

Delete your own recent messages in a channel/DM (optionally only those containing some text). Goes slowly to respect rate limits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "purge_my_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoOnly messages after this time (ISO8601)
limitNoMax messages of yours to delete (default 20, max 500)
dry_runNoOnly list what would be deleted
user_idNoOr: a user ID to DM (opens the DM for you)
containsNoOnly delete messages containing this text
channel_idNoChannel/thread/DM ID or a discord.com/channels/… link

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the irreversibility signal is carried structurally. The description adds a real behavioral trait beyond that: 'Goes slowly to respect rate limits,' which tells the agent to expect throttled, slow execution. It stops short of noting the dry_run escape hatch or per-run effects.

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?

Two compact sentences with the core action scoped first and the execution-speed caveat second. No redundant restatement of the name or title, and every clause carries 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?

For a destructive, zero-required-parameter tool, the description covers purpose, the text filter, and pacing. It omits what happens when no channel_id or user_id is supplied (the scope default), does not surface the DM-opening behavior of user_id, and never mentions dry_run, leaving meaningful gaps for an agent deciding how to invoke it safely.

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 100%, so all six parameters (after, limit, dry_run, user_id, contains, channel_id) are already documented in the schema, making baseline 3 appropriate. The description adds only the 'optionally only those containing some text' gloss, which partly duplicates the schema's own description of `contains`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Delete) and a precisely scoped resource (your own recent messages in a channel/DM) with an inline filter qualifier. The 'your own' scoping distinguishes it implicitly from bulk_delete_messages, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the scoping phrase 'your own recent messages' and the optional text filter, which suggests this is the self-targeted, narrow cleanup tool. However, there is no explicit when-to-use/when-not statement and no pointer to an alternative such as bulk_delete_messages for broader cleanup.

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