Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild

Destructive

Permanently deletes a Discord server you own, removing the guild irreversibly. Optionally record a reason in the audit log.

Instructions

Permanently delete a server you own. Irreversible. [DELETE /guilds/{guild_id}]

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": {
      "guild_id": "<guild_id>"
    },
    "name": "delete_guild"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already set destructiveHint=true and readOnlyHint=false, so 'Permanently... Irreversible' largely restates structured data. The one piece of genuinely additive context is the ownership requirement, which hints at an auth prerequisite, but the description omits cascade scope and recovery options that an agent about to fire an irreversible call would want.

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?

Three compact sentences with the irreversible warning front-loaded immediately after the action, so an agent skimming the first line gets the critical fact. The bracketed HTTP endpoint adds little for an agent and is the only filler.

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 two-parameter destructive tool with rich annotations and no output schema, the definition covers the essentials: what is destroyed, that it is permanent, and who may do it. It is not quite complete because cascade effects and the audit-log 'reason' parameter go unmentioned.

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 both parameters are already documented at the schema level, setting the baseline at 3. The description only echoes the guild_id path parameter and says nothing about the optional 'reason' audit-log field, so it adds no meaning beyond the schema.

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?

Names a specific verb and resource ('Permanently delete a server') with an ownership scope qualifier, which separates it from the many delete_guild_* siblings that remove sub-resources rather than the server itself. It stops short of explicitly naming any sibling, so differentiation is inferred from the resource noun rather than stated.

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?

'a server you own' implies a permission prerequisite, which is useful, but there is no explicit when-to-use versus when-not guidance and no mention of what happens to the guild's channels, roles, or messages when it is deleted. Usage context is implied rather than spelled out.

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