Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_channel_positions

Reorder Discord guild channels or move them between categories by updating channel positions and parent IDs. Use it to organize server layout and keep channel order consistent.

Instructions

Reorder channels / move them between categories. positions: [{id, position?, parent_id?, lock_permissions?}]. [PATCH /guilds/{guild_id}/channels]

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_channel_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

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation, and the description adds the underlying endpoint (PATCH /guilds/{guild_id}/channels). It omits what an agent most needs for a mutation: required MANAGE_CHANNELS permission, side effects on channels not listed, and the notoriously strict rate limit on this endpoint.

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?

Front-loaded with the action and resource, and the body-shape hint plus endpoint are compressed into a single compact block with no wasted words. The bracketed endpoint and terse object notation are slightly cryptic but not padded.

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?

For a mutating bulk-update tool with no output schema, the description covers the request body shape and endpoint but leaves out permission requirements, failure modes, and whether unlisted channels keep their positions — meaningful gaps for an agent planning an invocation.

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% for the top-level fields, but the schema types positions only as an untyped array ('items': {}) — the description supplies the actual item shape (id, position?, parent_id?, lock_permissions?), which is genuine information the schema lacks. It does not explain optional-field defaults or what omitting parent_id means.

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 names a specific verb pair ('Reorder channels / move them between categories') and the resource, which distinguishes it from modify_channel or modify_guild_role_positions. It stops short of explicitly naming a sibling to avoid, so it sits just below the top band.

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?

The purpose implies when to use it (bulk reordering or re-parenting channels), but there is no explicit statement of when-not-to-use it versus modify_channel or modify_channel_permissions, and no prerequisites such as required permissions.

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