Skip to main content
Glama
669px

Dc-MCP

by 669px

discord_move_channel

Move a Discord channel to a new position or category by specifying its ID, the desired position, and an optional category ID.

Instructions

Move a channel to a new position and/or category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNo
guild_idNo
positionYes
channel_idYes
category_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries the full burden of transparency. It discloses a mutation action and the changeable attributes, but says nothing about required permissions, ordering behavior, what 'position' means relative to category_id, or whether this can be undone.

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?

The description is one efficient sentence with no filler. It front-loads the core action and target, though additional behavioral context would improve it without harming conciseness.

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?

This is a mutating operation without annotations or schema descriptions, so the description is responsible for a lot. An output schema exists, but the description still lacks enough detail for an agent to confidently execute a move, especially regarding category/position interactions and any side effects.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must add parameter meaning. It does clarify that position and category are changeable and optional relative to each other, but it leaves 'channel_id', 'guild_id', and 'reason' completely unexplained and gives no context about position semantics or category_id behavior.

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 clearly states the action ('Move'), the resource ('a channel'), and the available new states ('new position and/or category'). It does not explicitly distinguish itself from the overlapping sibling 'discord_edit_channel', but the focus on moving is evident.

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?

No when-to-use or when-not-to-use guidance is provided. The description does not compare this operation to discord_edit_channel, which could also modify channel placement or settings, and there are no explicit conditions for selecting this tool.

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/669px/Dc-MCP'

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