Skip to main content
Glama

Copy a channel (admin)

discord_admin_clone_channel

Creates a new Discord channel by copying an existing channel's type, category, topic, permissions, slowmode, and forum settings so you can replicate structure without manual setup.

Instructions

Create a new channel with the same type, category, topic, permissions, slowmode and forum tags/settings as an existing one.

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": {
      "channel_id": "<channel_id>",
      "name": "<name>"
    },
    "name": "discord_admin_clone_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
reasonNoReason, recorded in Discord's audit log
channel_idYesChannel to copy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only supply the generic readOnly=false / destructive=false / openWorld=true profile, and the description adds genuine behavioral content by enumerating exactly which attributes are duplicated (type, category, topic, permissions, slowmode, forum tags/settings). It leaves out the authorization scope required to clone, whether channel position/sync state is preserved, and any failure modes, so it is strong but not exhaustive.

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?

A single sentence that front-loads the action and then lists the copied attributes in a compact, scannable clause. No filler, no repetition of the title, nothing that could be cut.

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?

With three parameters, no output schema and a safe-by-default annotation set, the definition covers what gets cloned, which is the central question. It omits what the call returns (presumably the new channel's id), required permissions, and edge cases such as cloning categories or unsupported channel types, leaving meaningful gaps for a mutation tool.

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 coverage is 67%: channel_id is documented as 'Channel to copy' and reason as the audit-log entry. The description adds no parameter-level meaning of its own — notably it never states that the required 'name' is the new channel's name or whether it must be unique in the guild — so it roughly matches the baseline for a partly documented 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 pairs a specific verb ('Create a new channel') with the distinguishing modifier 'with the same type, category, topic, permissions, slowmode and forum tags/settings as an existing one', which separates it from a plain create-channel tool. It stops short of explicitly naming the sibling it differs from (discord_admin_create_channel), so it is clear but not maximally differentiated.

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?

Usage is only implied: an agent can infer this is the tool for duplicating an existing channel's configuration rather than building one from scratch. There is no explicit when-to-use/when-not guidance, no mention of restrictions (e.g. unsupported channel types, permission prerequisites), and no routing to alternatives like create_channel or edit_channel.

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