discord-mcp

discord_set_role_position

Idempotent

Move a Discord role up or down the server role hierarchy to control permission precedence and member-list ordering.

Instructions

Move a role up or down in the server's role hierarchy, which determines permission precedence and member-list ordering. Higher position = higher in the list. Requires the Manage Roles permission, and the target position must be below the bot's highest role.

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": {
      "guild_id": "<guild_id>",
      "role_id": "<role_id>",
      "position": "<position>"
    },
    "name": "discord_set_role_position"
  }
}

Input Schema

Name	Required	Description
`role_id`	Yes	ID (snowflake) of the role to reposition.
`guild_id`	Yes	Discord server (guild) ID (snowflake).
`position`	Yes	New hierarchy position (1 = lowest, just above @everyone, which sits at 0). Higher numbers rank higher.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.0Sep 6, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed6 schema fields changedv2.0.0Jun 27, 2026

addedInput schema / properties / guild_id / pattern
```
Added value: +"^\\d{17,20}$"
```

changedInput schema / properties / position / description

Previous value: -"New hierarchy position (0 = lowest, just above @everyone). Higher numbers rank higher."New value: +"New hierarchy position (1 = lowest, just above @everyone, which sits at 0). Higher numbers rank higher."

addedInput schema / properties / position / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / position / minimum
```
Added value: +1
```

changedInput schema / properties / position / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / role_id / pattern
```
Added value: +"^\\d{17,20}$"
```

Changed3 schema fields changedv1.6.0May 28, 2026

addedInput schema / properties / guild_id / description

Added value: +"Discord server (guild) ID (snowflake)."

addedInput schema / properties / position / description

Added value: +"New hierarchy position (0 = lowest, just above @everyone). Higher numbers rank higher."

addedInput schema / properties / role_id / description

Added value: +"ID (snowflake) of the role to reposition."

Addedv1.5.0May 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, which already indicate a non-read-only, non-destructive, idempotent operation, the description discloses the permission requirement, the role-hierarchy constraint, and the behavioral consequence of moving the role. This gives the agent a clear model of what will happen and what conditions must hold before invoking the tool.

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?

The description is two sentences, front-loads the core action and effect, and includes only high-value operational details. There is no filler, repetition of the tool name, or redundant schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three required parameters, full schema coverage, and no output schema, the description covers the key call-side knowledge: what the operation does, how position works, what permission is needed, and the critical hierarchy constraint. Nothing essential for correctly selecting and invoking the tool is missing.

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?

The input schema already documents all three parameters with 100% coverage, including the position semantics. The description adds operational meaning to the position parameter by explaining that higher means higher in the list and by adding the constraint that the target position must be below the bot's highest role — information not present in 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?

The description uses a specific verb ('Move') and resource ('role') and clearly explains the effect on the server's role hierarchy, including permission precedence and member-list ordering. It is immediately distinguishable from siblings like discord_set_role_permission and discord_edit_role because it focuses solely on repositioning a role.

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 clear operational context: when repositioning a role in the hierarchy, it affects permission precedence and ordering. It also states important prerequisites — Manage Roles permission and the constraint that the target position must be below the bot's highest role — though it does not explicitly name alternative tools or say when not to use this tool.

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

Deploy Server