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

Import server template

import_server_template

Converts a Discord template link into a blueprint of its roles, categories, channels, and permissions so you can review or edit the structure before planning a server build.

Instructions

Turn a Discord server template link (discord.new/CODE or discord.com/template/CODE) into a blueprint: its roles, categories, channels, and who can see and post where. Nothing is built; plan the result with plan_server_build to build it on a server, after editing it if wanted. Optionally save it with save_as. The template's server settings (verification level, media filter, notifications) are listed for update_server, since blueprints do not carry them.

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": {
      "template": "<template>"
    },
    "name": "import_server_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
save_asNoSave the blueprint under this name.
templateYesThe template link or its code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and destructiveHint=false, so the description's 'Nothing is built' is genuinely load-bearing — it tells the agent that a non-readOnly tool still leaves the target server untouched. It also discloses a real side effect boundary (saved blueprint vs. server state) and the settings-omission caveat, though it is silent on whether save_as overwrites an existing blueprint name or what permissions are needed.

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 sentences, front-loaded with the core transformation, then the crucial 'nothing is built' constraint, then secondary notes. The parenthetical URL forms are compactly informative; no sentence is filler, though the settings sentence is slightly clause-heavy.

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?

With no output schema, the description carries the return burden and does it well by enumerating what the blueprint contains and noting that server settings come back separately. It stops short of describing the response's shape or how the blueprint is identified/referenced for plan_server_build.

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 coverage is 100%, so both parameters are already documented, including accepted link formats and the save_as name. The description only adds that save_as is optional and that the template accepts either a link or a bare code — useful but marginal over the schema, so the baseline 3 applies.

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 input ('Turn a Discord server template link ... into a blueprint') plus the exact contents produced (roles, categories, channels, visibility/post permissions). The 'Nothing is built' clause sharply separates it from plan_server_build and any create/sync sibling, so an agent can classify it without opening the 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?

Explicit routing follows the purpose: plan with plan_server_build to actually build, optionally persist with save_as, and use update_server for the settings that blueprints don't carry. It gives clear conditions for follow-on tools but never states when to prefer list_server_templates or create_server_template over importing.

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