Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_template

Updates an existing Discord server template's name or description using its guild ID and template code.

Instructions

Modify Guild Template. [PATCH /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": "modify_guild_template"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond them — no statement about what fields get changed, whether unspecified fields are preserved, or that an audit-log reason is recorded. With annotations present the bar is lower, but zero added context still warrants a low score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two terse fragments with no wasted words, but the brevity reflects under-specification rather than discipline — the endpoint bracket adds little for an agent and there is no front-loaded statement of effect or scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a mutation tool with no output schema and a large family of modify_* siblings, so the description should clarify what a template modification changes and when it is appropriate. Instead it supplies only the route, leaving the agent to infer behavior entirely from schema and annotations.

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 80% and every parameter carries at least a short description (name, description, guild_id, template_code, reason with its audit-log note). The description text contributes no additional meaning, so the schema carries the load and baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially the tool name restated ('Modify Guild Template') followed by the HTTP route. While the route hints at the resource hierarchy, no sentence explains what modifying a guild template actually entails or how it differs from create/delete/sync/use siblings.

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 at all: nothing says to use this rather than create_guild_template, sync_guild_template, or use_guild_template, and no prerequisites or exclusions are mentioned. The only directional hint is the PATCH verb, which the agent must interpret on its own.

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