Skip to main content
Glama

Reorder roles or channels (admin)

discord_admin_reorder
Destructive

Reorder Discord roles or channels within a category by name or ID to set top-to-bottom display order; unlisted items keep their relative order.

Instructions

Set the order of roles (top to bottom, below the bot's own role) or of channels inside one category (top to bottom, by name or ID). Items not listed keep their relative order after the listed ones.

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": {
      "what": "<what>",
      "order": "<order>"
    },
    "name": "discord_admin_reorder"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYes
orderYesNames or IDs, top first
reasonNoReason, recorded in Discord's audit log
category_idNochannels: the category whose channels to order (omit for channels outside categories)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the mutation profile is carried by structured data. The description does add one genuinely non-obvious behavior — unlisted items keep their relative order after the listed ones — which tells the agent this is a partial reorder, not a full overwrite. It still omits permission requirements and failure behavior for an operation flagged destructive.

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?

Two tight sentences with the action and scope front-loaded, followed by the partial-order rule. Every clause carries information; only the role/channel split makes it slightly dense to parse in one pass.

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

Completeness1/5

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

Placeholder.

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 75%, so the baseline is 3. The description reinforces two things already in the schema — that 'order' is top-first and accepts names or IDs, and that category_id scopes channel ordering — but adds no semantics the schema lacks, such as how duplicate or unknown names are treated.

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 states a specific verb (Set the order) plus both resources (roles or channels) and the exact axis of ordering (top to bottom). The parenthetical constraints — roles are placed below the bot's own role, channels must be inside one category — make the scope unambiguous and distinguish it from edit_role/edit_channel siblings that mutate other attributes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied: use it when you need to change display ordering, and the 'below the bot's own role' note hints at a prerequisite condition. However, it never states required permissions (Manage Roles), when to prefer this over editing a role/channel, or what happens if the operation is impossible, so alternatives and exclusions are left to inference.

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