Skip to main content
Glama

discord_edit_channel

Modify Discord channel properties including name, topic, and slowmode settings to manage server organization and communication flow.

Instructions

Edit a channel's name, topic (text only) or slowmode (text only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
nameNo
topicNo
slowmodeNoSlowmode in seconds (0 to disable).

Implementation Reference

  • The handler implementation for discord_edit_channel, which fetches the channel and applies edits for name, topic, and slowmode.
    case "discord_edit_channel": {
      const channel = await getGuildChannel(args.channel_id as string);
      const editOptions: Record<string, unknown> = {};
      if (args.name !== undefined) editOptions.name = args.name as string;
      if (args.topic !== undefined && channel.type === ChannelType.GuildText) editOptions.topic = args.topic as string;
      if (args.slowmode !== undefined && channel.type === ChannelType.GuildText) editOptions.rateLimitPerUser = args.slowmode as number;
      await channel.edit(editOptions);
      return { content: [{ type: "text", text: `✅ Channel #${channel.name} updated.` }] };
    }
  • The JSON schema definition for the discord_edit_channel tool.
      name: "discord_edit_channel",
      description: "Edit a channel's name, topic (text only) or slowmode (text only).",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          name: { type: "string" },
          topic: { type: "string" },
          slowmode: { type: "number", description: "Slowmode in seconds (0 to disable)." },
        },
        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 of behavioral disclosure. It mentions the editable fields but doesn't cover critical aspects like required permissions, whether the edit is reversible, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 front-loads the core action ('Edit') and lists the editable fields clearly, 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 the tool's complexity (a mutation with 4 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't address permissions, error conditions, or response format, which are crucial for an agent to use this tool effectively in a Discord context.

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 25% (only 'slowmode' has a description). The description adds value by clarifying that 'topic' and 'slowmode' are text-only, which isn't in the schema, and implies these are optional parameters. However, it doesn't fully compensate for the low coverage, as 'channel_id' and 'name' remain undocumented in both schema and description.

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 ('Edit') and resource ('a channel's name, topic, or slowmode'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'discord_edit_message' or 'discord_edit_role', which share the same 'edit' verb pattern but target different resources.

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. For example, it doesn't mention prerequisites (e.g., needing channel permissions), when not to use it (e.g., for editing other channel properties not listed), or how it differs from related tools like 'discord_move_channel' or 'discord_reset_channel_permissions'.

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