Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_role_positions

Reorder Discord server roles by specifying role IDs and target positions to change hierarchy order and permission priority in a guild.

Instructions

Reorder roles. positions: [{id, position}]. [PATCH /guilds/{guild_id}/roles]

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>",
      "positions": "<positions>"
    },
    "name": "modify_guild_role_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
positionsYesArray body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the HTTP endpoint and body shape; it says nothing about required permissions (MANAGE_ROLES), whether unlisted roles are left untouched, or that ordering is guild-wide and can break hierarchies — all critical for a bulk mutation.

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?

Three terse fragments, action first, then payload shape, then endpoint. Nothing is wasted, though the extreme terseness leaves no room for the usage and behavior context the tool needs.

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

Completeness2/5

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

For a three-parameter bulk mutation with no output schema, the definition omits permission requirements, the effect on roles not listed, and the consequence of conflicting positions. Annotations cover only the safe/unsafe axis, so the description should carry more of this burden.

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 the baseline would be 3, but the schema describes positions merely as "Array body" with empty item definitions. The description's "positions: [{id, position}]" fills that real gap by revealing the element structure an agent must construct.

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?

"Reorder roles" is a specific verb+resource that is clearly distinct from single-role operations like modify_guild_role or create_guild_role. It stops short of explicitly contrasting itself with those siblings, but the purpose is unambiguous.

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 versus modify_guild_role (single role edit) or modify_guild_channel_positions, and no stated prerequisites. The agent must infer from the name alone that this is the bulk reordering path.

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

Deploy Server

Other Tools