Skip to main content
Glama

discord_clone_channel

Clone Discord channels with their names, topics, and permission settings to replicate channel configurations across servers.

Instructions

Clone a channel with its name, topic and permission overwrites.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
new_nameNo

Implementation Reference

  • The implementation of the 'discord_clone_channel' tool handler, which fetches the original channel and performs a clone operation.
    case "discord_clone_channel": {
      const channel = await getGuildChannel(args.channel_id as string);
      const cloned = await channel.clone({ name: args.new_name as string | undefined });
      return { content: [{ type: "text", text: `✅ Channel cloned as #${cloned.name} (id: ${cloned.id}).` }] };
    }
  • The definition and input schema for the 'discord_clone_channel' tool.
      name: "discord_clone_channel",
      description: "Clone a channel with its name, topic and permission overwrites.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          new_name: { 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 the full burden. It mentions cloning 'permission overwrites', hinting at a mutation operation, but doesn't disclose critical behaviors: whether this requires admin permissions, if it's destructive to the original channel, rate limits, or what the output looks like (e.g., new channel ID). This leaves significant gaps for an agent to use it safely.

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 with no wasted words. It front-loads the core action ('Clone a channel') and specifies key attributes. Every part earns its place by clarifying scope, making it easy to scan and understand 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 the complexity (a mutation tool with no annotations, 0% schema coverage, and no output schema), the description is incomplete. It lacks behavioral details (e.g., permissions, side effects), doesn't fully explain parameters, and offers no usage context. For a tool that likely modifies server state, this is inadequate to guide an agent effectively.

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 compensate. It implies parameters for cloning ('name, topic and permission overwrites'), but only loosely maps to the two parameters in the schema ('channel_id', 'new_name'). It doesn't explain what 'channel_id' is (e.g., source channel) or if 'new_name' is optional, missing details like topic handling or permission specifics. This adds minimal value beyond the bare schema.

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 verb ('Clone') and resource ('a channel'), specifying what gets cloned ('its name, topic and permission overwrites'). It distinguishes from siblings like 'discord_create_channel' by focusing on duplication rather than creation from scratch. However, it doesn't explicitly contrast with 'discord_copy_permissions', which might handle permission copying separately.

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 guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this should be used instead of 'discord_create_channel' for replicating settings, or mention prerequisites like required permissions. The description only states what it does, not when or why to use it.

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