Discord MCP - Discord server management MCP for AI agents

Reorder roles

reorder_roles

Move Discord roles to new hierarchy positions in one call, previewing permission-impacting changes before confirming with a token.

Instructions

Move roles to new hierarchy positions in one call. Higher positions sit higher in the list and outrank lower ones. Moving a role that can ban, kick, time out, rename, or change roles above a role it was below lets its holders do that to the people with the other role, so that needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

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_roles"
  }
}

Input Schema

Name	Required	Description
`guild`	No	Guild (server) name or ID. Omit to use the default guild.
`moves`	Yes
`confirm_token`	No	The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields 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"

addedInput schema / properties / confirm_token

Added value: +{
+  "description": "The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.",
+  "type": "string"
+}

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

A3.8/5.0

Behavior3/5

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

The definition discloses the most important behavior beyond annotations: the two-phase preview/confirm flow, that the first call mutates nothing, and the privilege-escalation consequence of moving a powerful role upward. Annotations (readOnlyHint=false, destructiveHint=false) already cover the safety profile, and the escalation warning is a genuine supplement rather than a conflict. What is missing is whether other roles' positions are renumbered or shifted, and what the preview actually contains.

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?

Purpose is front-loaded and every clause carries information; nothing is padded or restated from the title. The second sentence is long and chains the permission explanation with the confirm flow, which costs some readability but not correctness.

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 three-parameter mutation tool with no output schema, the definition covers the risky parts an agent would otherwise get wrong: the preview/confirm sequence and the privilege side effects. It would be complete at a 5 if it stated what the preview returns or how conflicting/duplicate positions in the moves array are handled.

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 a middling 67%, and the description compensates by explaining that a higher position means higher rank and outranks lower ones — meaning for the `position` parameter that the schema does not state. It also ties confirm_token to the preview flow, though `guild` and the shape of each move object are left entirely to the schema.

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 opening clause gives a specific verb and resource ("Move roles to new hierarchy positions") plus a scope note ("in one call"), which is unambiguous about what changes. It does not explicitly distinguish itself from bulk_update_roles or clone_role, so an agent facing several role-mutation siblings must infer the difference from names alone.

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 gives concrete operational guidance: the first call is a no-op preview, and the change happens only on a repeat call carrying the returned confirm_token. That is exactly the when/how an agent needs. It stops short of stating when to prefer this over bulk_update_roles or list_roles for checking current ordering.

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

Deploy Server