Discord MCP - Discord server management MCP for AI agents

Reorder channels

reorder_channels

Move Discord channels to new positions and optionally into different categories in a single call, keeping server layout organized without multiple separate updates.

Instructions

Move channels to new positions, and optionally into a different category, in one call.

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": {
      "moves": "<moves>"
    },
    "name": "reorder_channels"
  }
}

Input Schema

Name	Required	Description	Default
`guild`	No	Guild (server) name or ID. Omit to use the default guild.
`moves`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.4.2Nov 12, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed3 schema fields changedv1.3.0Aug 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / moves / items / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / moves / items / properties / position / maximum
```
Added value: +9007199254740991
```
First observedv1.0.2Jun 14, 2026

TDQS

B3.2/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 safety is partly covered. The phrase 'in one call' usefully signals a batched mutation, but the description does not say whether the batch is atomic, what happens if one move fails, or what permissions are needed. For a bulk mutation over a nested array, that leaves real behavioral gaps.

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 sentence, front-loaded with the primary action, with no filler. It is arguably slightly too terse for a batched mutation, but nothing in it is wasted.

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?

With only two top-level parameters, no output schema, and annotations covering the safety profile, the definition is close to sufficient. The missing pieces are permission requirements and failure/atomicity behavior for the moves array, which matter for a write operation but are not described.

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 50% (guild, channel, and category are documented; position is not), so the description carries partial burden. It does add that category placement is optional, which clarifies the category field's semantics beyond the schema's 'or none for top level' wording. It says nothing about how position values are interpreted (absolute index vs. relative) or how they interact with category moves.

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?

The description uses a specific verb ('Move channels') on a specific resource and states the two effects: new positions and optionally a new category. It is clearly distinguishable from the nearest sibling, reorder_roles, because the resource is named explicitly. It stops short of a 5 because it does not name any alternative tool or scoping qualifier.

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 guidance on when to use this instead of creating/deleting channels or moving them individually, and no prerequisites such as requiring Manage Channels permission or an existing category. The reader must infer the use case entirely from the one-line purpose.

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

Deploy Server