Skip to main content
Glama

discord_move_channel

Move Discord channels between categories or remove them from categories to organize server structure efficiently.

Instructions

Move a channel into a category (or remove from category if category_id is omitted).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
category_idNo

Implementation Reference

  • The handler for discord_move_channel which fetches the channel and edits its parent (category).
    case "discord_move_channel": {
      const channel = await getGuildChannel(args.channel_id as string);
      await channel.edit({ parent: (args.category_id as string | undefined) ?? null });
      return { content: [{ type: "text", text: `✅ Channel #${channel.name} moved.` }] };
    }
  • The schema definition for discord_move_channel.
      name: "discord_move_channel",
      description: "Move a channel into a category (or remove from category if category_id is omitted).",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          category_id: { type: "string" },
        },
        required: ["channel_id"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the action ('move' and 'remove') but doesn't disclose behavioral traits like required permissions, whether it's destructive (likely yes, as it modifies channel structure), rate limits, or error conditions. The description is minimal and misses key operational details.

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, efficient sentence that front-loads the main action and includes a parenthetical nuance. There is zero waste, making it easy to parse quickly.

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?

Given no annotations, no output schema, and 2 parameters with 0% schema coverage, the description is incomplete. It covers the basic purpose and parameter intent but lacks details on behavior, permissions, errors, or return values, which are critical for a mutation tool in a complex system like Discord.

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 0%, so the description must compensate. It adds meaning by explaining that 'category_id' is optional and omitting it removes the channel from a category, which clarifies the parameter's role beyond the schema. However, it doesn't explain 'channel_id' semantics or provide format details, leaving gaps for a tool with 2 parameters.

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 a channel into a category') and the resource ('channel'), with an additional nuance about removing from a category. It distinguishes from siblings like 'discord_edit_channel' by focusing specifically on category placement, though it doesn't explicitly contrast with all siblings.

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 explicit guidance on when to use this tool versus alternatives like 'discord_edit_channel' (which might handle category changes) or 'discord_create_channel' (for initial placement). The description implies usage for category management but lacks context about prerequisites, permissions, or edge cases.

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/PaSympa/discord-mcp'

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