Skip to main content
Glama

discord_create_channel

Create text, voice, or category channels in Discord servers to organize communication spaces for different topics or purposes.

Instructions

Create a text, voice channel or category in a guild.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes
nameYes
typeNoDefaults to 'text'.
topicNo
category_idNo

Implementation Reference

  • The handler logic for 'discord_create_channel' which fetches the guild, determines the channel type, and creates the channel via the discord.js client.
    case "discord_create_channel": {
      const guild = await discord.guilds.fetch(validateId(args.guild_id, "guild_id"));
      const typeMap: Record<string, ChannelType> = {
        text: ChannelType.GuildText, voice: ChannelType.GuildVoice, category: ChannelType.GuildCategory,
      };
      const channelType = typeMap[(args.type as string) ?? "text"] ?? ChannelType.GuildText;
      const created = await guild.channels.create({
        name: args.name as string, type: channelType as ChannelType.GuildText | ChannelType.GuildVoice | ChannelType.GuildCategory,
        topic: channelType === ChannelType.GuildText ? (args.topic as string | undefined) : undefined,
        parent: args.category_id as string | undefined,
      });
      return { content: [{ type: "text", text: `✅ Channel #${created.name} created (id: ${created.id}).` }] };
    }
  • The schema definition for 'discord_create_channel' outlining the required and optional arguments.
    {
      name: "discord_create_channel",
      description: "Create a text, voice channel or category in a guild.",
      inputSchema: {
        type: "object",
        properties: {
          guild_id: { type: "string" },
          name: { type: "string" },
          type: { type: "string", enum: ["text", "voice", "category"], description: "Defaults to 'text'." },
          topic: { type: "string" },
          category_id: { type: "string" },
        },
        required: ["guild_id", "name"],
      },
    },
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 states the tool creates channels but fails to mention critical aspects like required permissions, rate limits, whether the operation is idempotent, or what happens on success/failure. This leaves significant gaps for an agent to understand the tool's behavior 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 that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, 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 complexity of creating a Discord channel (a mutation operation with 5 parameters), no annotations, and no output schema, the description is inadequate. It lacks details on permissions, error handling, return values, and interactions with other tools, leaving the agent with insufficient context to use the tool effectively.

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 low at 20%, with only the 'type' parameter documented. The description mentions 'text, voice channel or category', which aligns with the enum for 'type', but adds no details about other parameters like 'guild_id', 'name', 'topic', or 'category_id'. It partially compensates for the schema gap but not sufficiently for the undocumented 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 ('Create') and the resource ('text, voice channel or category in a guild'), which distinguishes it from siblings like discord_delete_channel or discord_edit_channel. However, it doesn't explicitly differentiate from discord_create_forum_channel, which creates a different channel type, leaving some ambiguity.

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_create_forum_channel or discord_clone_channel. It lacks context about prerequisites (e.g., permissions needed) or typical use cases, offering only a basic functional statement without usage boundaries.

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