Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by cappyeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

interactions_delete_followup

DestructiveIdempotent

Delete a follow-up Discord message permanently. Requires explicit confirmation and dry-run mode disabled to complete the irreversible action.

Instructions

Purpose: Delete a follow-up message. DESTRUCTIVE - IRREVERSIBLE.

Auth: token-secured (NO bot token).

Returns: {deleted, message_id}. Pass __confirm:true AND MCP_DRY_RUN=false to actually delete.

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": {
      "application_id": "<application_id>",
      "interaction_token": "<interaction_token>",
      "message_id": "<message_id>"
    },
    "name": "interactions_delete_followup"
  }
}

Input Schema

NameRequiredDescriptionDefault
__confirmNoSet true to authorize this destructive operation. Also requires the server to run with MCP_DRY_RUN=false; otherwise a DRY_RUN_PREVIEW is returned.
message_idYesFollow-up message id
application_idYesBot/app application ID
interaction_tokenYesScoped interaction credential, reusable for follow-ups for up to 15 minutes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.22.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true), the description adds critical behavioral details: irreversibility, auth specifics (token-secured, no bot token), return payload, and the dry-run/confirmation gate. This provides substantial value beyond what annotations convey.

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?

The description is compact, using bold labels for Purpose, Auth, and Returns. Each sentence is purposeful: it covers what the tool does, safety, authorization, and critical execution requirements. No filler or redundancy.

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 tool with a 4-parameter schema and output schema, the description covers all essential aspects: purpose, irreversibility, auth, return format, and the confirmation/dry-run mechanism. The presence of an output schema means return-value explanation is not necessary. It is sufficient for an agent to invoke safely.

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?

The input schema already documents all parameters with descriptions (100% coverage), so the baseline is 3. The description adds meaningful context for __confirm (requires MCP_DRY_RUN=false) and emphasizes the interaction_token's scoped nature, which goes beyond the schema's field-level descriptions.

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?

The description clearly states the action: 'Delete a follow-up message.' It uses a specific verb and resource, making it distinct from sibling tools like messages_delete or interactions_delete_original_response. The destructive and irreversible nature is also highlighted upfront.

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?

The description provides explicit usage requirements (pass __confirm:true AND MCP_DRY_RUN=false) and auth constraints, which are helpful. However, it does not explicitly contrast with alternatives or state when to choose this tool over similar deletion tools. The context is clear from the resource name but lacks direct alternative guidance.

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