Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a message

delete_message
Destructive

Deletes one Discord message, including the bot's own or any message with Manage Messages; returns a dry run unless confirm is true, and bulk deletion handles multiple messages.

Instructions

Deletes one message (the bot's own, or anyone's with Manage Messages). Destructive: returns a dry run unless confirm is true. For many messages use bulk_delete_messages (moderation pack).

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": {
      "message": "<message>"
    },
    "name": "delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNoInstead of channel: a user (ID, <@mention> or name) whose DM channel to use.
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
reasonNo
channelNoChannel or thread: ID, <#mention>, link, or name. Archived threads by ID or link.
confirmNoSet to true to actually do it. Without it, nothing changes and a dry run is returned.
messageYesMessage ID or message link (https://discord.com/channels/...). With a link, channel is optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavior: the call returns a dry run unless confirm is true, and the permission gate on whose messages can be removed. It does not discuss irreversibility/recovery or rate limits, which keeps it short of a 5.

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?

Two tight sentences, with the destructive dry-run gate and the alternative-tool routing front-loaded where they matter most. Slightly compressed phrasing ("For many messages use...") is efficient rather than unclear.

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 6-parameter destructive tool with no output schema, the description covers the essential decision points: single vs bulk, permission requirement, and dry-run-by-default. The only gap is the audit-log reason parameter, which is unexplained in both schema and description but is ancillary to correct invocation.

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 83%, so the schema already explains message, confirm, channel, guild, and user. The description only reinforces the confirm/dry-run gate and the 'one message' scope, adding little semantic detail beyond the structured fields; the undescribed reason parameter is not covered either.

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 ("Deletes one message") and immediately scopes it with permission context ("the bot's own, or anyone's with Manage Messages") and cardinality (one, not many). An agent can distinguish it from edit_message, get_message, and bulk deletion without opening any 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 an explicit routing rule: use this for a single message, use bulk_delete_messages (moderation pack) for many. It also names the permission prerequisite that determines whether the call will even succeed, leaving nothing for the agent to infer.

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