discord-server-mcp

import_discord_template

Read-only

Load a Discord server template from a link and return it as an editable blueprint for previewing and building, along with its name, description, and usage count.

Instructions

Load a Discord server template from a link (discord.new/CODE or discord.com/template/CODE, as shared on template websites) and return it as a blueprint you can show with preview_blueprint, edit, and build with apply_blueprint. Also gives the template's name, description and how many times it was used.

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": {
      "link": "<link>"
    },
    "name": "import_discord_template"
  }
}

Input Schema

Name	Required	Description	Default
`bot`	No	Use this bot (name or id) instead of choosing automatically
`link`	Yes	Template link or code

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that (it only loads and returns data). It adds useful behavior beyond the annotations: the returned object includes the template's name, description, and use count, not just the blueprint. Minor gaps remain around error handling for bad links.

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?

One dense sentence that front-loads the action and immediately routes to the follow-on tools. Slight redundancy between 'return it as a blueprint' and the trailing metadata clause, but nothing gratuitous.

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 two-parameter read-only import with no output schema, the description covers what goes in, what comes back, and what to do next. It could say more about failure modes or whether the returned blueprint is editable locally before applying, but the essentials are present.

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 100%, so baseline is 3, but the description earns an extra point by documenting accepted link forms (discord.new/CODE or discord.com/template/CODE) and noting that a bare code also works, which the schema does not state. It says nothing about the optional 'bot' parameter, leaving that to the schema.

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?

Specific verb ('Load') plus resource ('Discord server template from a link') plus the output ('blueprint'). It names the sibling tools that consume the result (preview_blueprint, apply_blueprint), so an agent can place it in the workflow without opening other schemas.

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?

The description makes the pipeline explicit: import, then show with preview_blueprint, edit, then build with apply_blueprint. That is clear usage context, though it offers no exclusions or caveats such as what happens with an invalid or expired link.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.