Skip to main content
Glama
TheETR

TheeDiscordMCP

by TheETR

discord_reorder_channels

Bulk reorder Discord channels and move them between categories. Dry run mode previews changes before applying.

Instructions

Bulk reorder channels and optionally move them between categories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNo
reasonNo
guildIdYes
positionsYes
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits but fails to mention the dryRun default (true) or that the operation may not persist changes. It also omits permissions, reversibility, and potential side effects, offering only superficial insight into bulk reordering.

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 a single, concise sentence that is front-loaded with the action and includes the key qualifiers 'Bulk' and 'optionally move between categories' without wasted words. It is efficiently structured.

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?

As a mutation tool with no annotations and no output schema, the description is too sparse. It omits critical context such as the dryRun default, permission requirements, and what happens to existing channel arrangements. This leaves an agent uncertain about the tool's full behavior and prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no parameter-specific information. The four parameters (guildId, positions, dryRun, reason) are not mentioned, leaving agents to infer meaning solely from property names. This does not compensate for the schema's lack of descriptions.

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 the specific verb 'reorder' and resource 'channels,' and adds the qualifier 'Bulk' and 'optionally move them between categories,' making its function clear. This distinguishes it from sibling tools like discord_reorder_roles and other channel management tools.

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 description implies the tool is for reordering channels but does not explicitly state when to use it versus alternatives or provide exclusions. It lacks a targeted 'use this for X, use that for Y' guidance that would earn a higher score.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TheETR/TheeDiscordMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server