discord-server-mcp

export_server_structure

Read-only

Export a Discord server's roles, categories, channels, topics, forum tags and permissions as a reusable JSON blueprint backup, so you can rebuild the same structure on this or another server.

Instructions

Export a server's roles, categories, channels, topics, forum tags and permissions as a blueprint (a backup without messages). Optionally save it to a JSON file; apply_blueprint can rebuild from it here or on another server.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_server_structure"
  }
}

Input Schema

Name	Required	Description
`bot`	No	Use this bot (name or id) instead of choosing automatically
`server`	No	Server name or id. Optional when the bot is in one server or DISCORD_GUILD_ID is set.
`save_to`	No	File path to write the JSON to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), and the description adds genuinely new behavioral context: the export deliberately excludes messages, and the result can optionally be persisted to a JSON file. No mention of required permissions or export size limits, but the scope disclosure is the more valuable piece.

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 sentences, front-loaded with the export scope, then the optional persistence and the downstream apply_blueprint path. Every clause carries information with no filler.

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 read-only export with full schema coverage and no output schema, the description covers scope, optional file persistence, and the consumer of the output. It leaves slightly ambiguous what is returned when save_to is omitted (blueprint data in the response?), which is the only real gap.

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%, so bot, server, and save_to are already documented; baseline 3 applies. The description only reinforces that saving to file is optional and what the file contains, adding little syntax or defaulting detail beyond 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?

States a specific verb (Export) plus the exact resource set — roles, categories, channels, topics, forum tags, permissions — and defines the term 'blueprint' inline as 'a backup without messages'. It is clearly distinguishable from apply_blueprint, which rebuilds rather than exports.

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?

Implies the backup use case and names the complementary sibling apply_blueprint for rebuilding 'here or on another server', which tells the agent what this output feeds into. It stops short of explicit when-not-to-use guidance (e.g. versus import_discord_template), but the direction is clear.

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