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

Sync server template

sync_server_template

Updates a Discord server template to match the server's current structure, keeping the template aligned with existing channels and roles.

Instructions

Update a template to match the server's current structure.

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": "sync_server_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesTemplate code from list_server_templates, or its discord.new link.
guildNoGuild (server) name or ID. Omit to use the default guild.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 from list_server_templates."New value: +"Template code from list_server_templates, 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*$"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds that the template's contents are overwritten to match the server, which is useful context beyond the annotations, but it does not say whether prior template state is recoverable, what permissions are required, or what happens if the template does not exist.

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?

A single front-loaded sentence with no wasted wording, and the direction of synchronization is stated up front. It is efficient but so terse that a clause about overwrite behavior would have earned its place.

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 mutation tool with no output schema, the definition covers the essential action and annotations cover safety, but it omits overwrite scope, permission requirements, and failure behavior. Adequate to select the tool, not fully adequate to predict its effects.

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%, with both `code` and `guild` documented in the schema itself, including the accepted link/code format and the default-guild behavior. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Update a template') plus the direction of the sync ('to match the server's current structure'), which lets an agent distinguish it from import_server_template (server-from-template) and create/delete siblings. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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?

Usage is only implied: the agent can infer this is the tool to run when a template has drifted from the live server structure. There is no explicit when-to-use statement, no prerequisites (e.g., template ownership), and no named alternative for the reverse direction.

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