Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete forum post

delete_forum_post
Destructive

Deletes a Discord forum post and every reply after a preview; repeat with the confirm token to execute deletion.

Instructions

Delete a forum post and every reply in it. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it.

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": {
      "post": "<post>"
    },
    "name": "delete_forum_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesPost title or thread ID.
guildNoGuild (server) name or ID. Omit to use the default guild.
reasonNo
dry_runNo
confirm_tokenNoThe token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token / description
      Added value: +"The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree."
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.2/5.0
Behavior4/5

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

With destructiveHint=true already declared, the description still adds real value: it discloses that all replies are destroyed and that a preview/confirm_token handshake gates the actual deletion, including that the preview mutates nothing. It falls short of fully disclosing irreversibility, required permissions, or side effects on attachments/reactions, and the unconditional 'first call changes nothing' framing sits awkwardly beside an unexplained dry_run parameter.

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 tight sentences: the destructive scope leads, followed by the safe-call procedure. Nothing is repeated and nothing is padding.

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 5-parameter destructive tool with no output schema, the description covers the essentials an agent needs to avoid an accidental deletion: cascading scope and the confirm-token gate. It is not fully complete, since permission requirements, irreversibility, and dry_run semantics relative to the preview flow are left unstated.

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 60% and the description only enriches the confirm_token workflow, which the schema already describes. The reason, guild, and especially dry_run parameters get no clarification from the description, and the implicit preview behavior leaves an agent unsure how dry_run interacts with the token flow.

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 opens with a precise verb and resource ('Delete a forum post') and immediately qualifies scope with 'and every reply in it', which distinguishes it from siblings like update_forum_post or delete_thread. The cascading-delete scope is stated up front so an agent knows the blast radius before selecting it.

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?

It gives clear operational guidance for how to invoke it safely ('Safe to call directly', first call previews, second with token deletes), which is exactly what an agent needs before touching a destructive tool. However, it never names or rules out alternatives such as delete_thread for thread-shaped content, so routing guidance is incomplete.

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