Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild_template

Destructive

Delete a Discord server template by guild ID and template code, optionally adding an audit-log reason.

Instructions

Delete Guild Template. [DELETE /guilds/{guild_id}/templates/{template_code}]

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>",
      "template_code": "<template_code>"
    },
    "name": "delete_guild_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
template_codeYesServer template code (discord.new/xyz)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so safety is covered structurally. The description adds only the endpoint mapping; it says nothing about irreversibility, whether existing uses of the template break, required permissions, or rate limits.

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 short fragments, front-loaded with the action and followed by the endpoint. There is no filler, though the brevity comes at the cost of substance rather than being a model of efficiency.

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?

With a fully described 3-parameter schema, complete annotations, and no output schema, the definition covers the mechanical basics. For a destructive operation it is still thin: no warning about irreversibility or effects on consumers of the template is provided.

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 guild_id, template_code, and the optional audit-log 'reason' are already documented in the schema. The description contributes no additional parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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?

The description names a specific verb and resource ('Delete Guild Template') and reinforces it with the exact REST path DELETE /guilds/{guild_id}/templates/{template_code}, so there is no ambiguity about what is removed. It does not, however, differentiate this from siblings such as delete_guild or modify_guild_template beyond the name itself.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite (e.g., MANAGE_GUILD permission), and no mention of alternatives such as modify_guild_template for edits or delete_guild for removing the whole server. The agent must infer usage entirely from the name.

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