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 server template

delete_server_template
Destructive

Delete a Discord server template so its share link stops working. The first call returns a preview and confirm_token; repeat with the token to complete deletion.

Instructions

Delete a server template; its share link stops working. 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": {
      "code": "<code>"
    },
    "name": "delete_server_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesTemplate code, or its discord.new link.
guildNoGuild (server) name or ID. Omit to use the default guild.
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. Changed4 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"
    • changedInput schema / properties / code / description
      Previous value: -"Template code."New value: +"Template code, or its discord.new link."
    • addedInput schema / properties / code / pattern
      Added value: +"^\\s*(?:(?:https?:\\/\\/)?(?:discord\\.new|discord(?:app)?\\.com\\/template)\\/)?[A-Za-z0-9-]{2,64}\\s*$"
    • 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.6/5.0
Behavior5/5

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

Annotations only flag destructiveHint=true; the description adds the crucial behavioral trait that the first call is a no-op preview returning a confirm_token and that deletion occurs only on the repeat call. It also discloses the user-facing side effect (share link stops working) and the confirmation-dialog behavior, which is exactly the extra context an agent needs before invoking a destructive tool.

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 with the consequence front-loaded and the invocation protocol immediately after; no filler and no restatement of the title.

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 destructive four-parameter tool with no output schema, the description covers the deletion effect, the confirmation workflow, and the token reuse condition. Minor gaps remain: it never names the guild scoping parameter or spells out what the preview contains beyond the token.

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?

Schema coverage is 75% and already documents code and confirm_token, but the description explains the two-call protocol that gives dry_run and confirm_token their meaning in combination, which the schema lists separately. It does not address the guild parameter, so it is not fully compensating for the remaining coverage gap.

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 ('Delete a server template') plus the concrete observable consequence ('its share link stops working'), which lets an agent distinguish it from create/import/sync/update template siblings without opening a schema.

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?

Gives a clear directive on how to invoke it ('Safe to call directly') and explains the preview-then-confirm sequence, so an agent knows the expected call pattern. It does not explicitly state when to prefer it over a non-destructive alternative (e.g. update_server) or any prerequisites, so it stops short of full when/when-not 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