Skip to main content
Glama

discord_copy_permissions

Copy permission overwrites from one Discord channel to another to maintain consistent access controls across channels.

Instructions

Copy all permission overwrites from one channel to another.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_channel_idYes
target_channel_idYes
reasonNo

Implementation Reference

  • Implementation of the 'discord_copy_permissions' tool handler, which fetches the source and target channels and sets the target's permission overwrites to match the source.
    case "discord_copy_permissions": {
      const source = await getGuildChannel(args.source_channel_id as string);
      const target = await getGuildChannel(args.target_channel_id as string);
      const overwrites = source.permissionOverwrites.cache.map((ow) => ({
        id: ow.id, type: ow.type, allow: ow.allow, deny: ow.deny,
      }));
      await target.permissionOverwrites.set(overwrites, args.reason as string | undefined);
      return { content: [{ type: "text", text: `✅ Permissions copied from #${source.name} to #${target.name}.` }] };
    }
  • Tool definition and schema for 'discord_copy_permissions', specifying required arguments source_channel_id and target_channel_id.
      name: "discord_copy_permissions",
      description: "Copy all permission overwrites from one channel to another.",
      inputSchema: {
        type: "object",
        properties: {
          source_channel_id: { type: "string" },
          target_channel_id: { type: "string" },
          reason: { type: "string" },
        },
        required: ["source_channel_id", "target_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 states this is a copy operation but doesn't disclose whether this overwrites existing permissions on the target channel, requires specific bot permissions, has rate limits, or what happens on failure. For a permission-modifying tool, this is a significant gap in behavioral context.

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 zero wasted words. It's appropriately sized for the tool's apparent complexity and gets straight to the point without unnecessary elaboration.

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?

For a permission-copying tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'permission overwrites' are, what gets copied exactly, whether the operation is idempotent, or what the expected outcome looks like.

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 schema provides no parameter documentation. The description mentions 'from one channel to another' which implies source and target channels, but doesn't explain the 'reason' parameter or provide any format details for channel IDs. It adds minimal value beyond what's inferable from the parameter names.

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 ('copy all permission overwrites') and resources involved ('from one channel to another'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'discord_clone_channel' or 'discord_set_role_permission', which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives like 'discord_clone_channel' (which might copy more than just permissions) or 'discord_reset_channel_permissions' (which might clear permissions). There's no mention of prerequisites, constraints, or typical use 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