Skip to main content
Glama

discord_create_forum_channel

Create a forum channel in a Discord server to organize discussions with specific topics and guidelines.

Instructions

Create a new forum channel in a guild.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes
nameYes
topicNoThe forum channel guidelines/topic.
category_idNoParent category ID (optional).

Implementation Reference

  • Implementation of the discord_create_forum_channel tool handler.
    case "discord_create_forum_channel": {
      const guild = await discord.guilds.fetch(validateId(args.guild_id, "guild_id"));
      const created = await guild.channels.create({
        name: args.name as string,
        type: ChannelType.GuildForum,
        topic: args.topic as string | undefined,
        parent: args.category_id as string | undefined,
      });
      return { content: [{ type: "text", text: `✅ Forum channel #${created.name} created (id: ${created.id}).` }] };
    }
  • Tool definition and input schema for discord_create_forum_channel.
    {
      name: "discord_create_forum_channel",
      description: "Create a new forum channel in a guild.",
      inputSchema: {
        type: "object",
        properties: {
          guild_id: { type: "string" },
          name: { type: "string" },
          topic: { type: "string", description: "The forum channel guidelines/topic." },
          category_id: { type: "string", description: "Parent category ID (optional)." },
        },
        required: ["guild_id", "name"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't mention permission requirements, rate limits, whether this is an idempotent operation, what happens on failure, or what the response looks like. For a creation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 gets straight to the point with zero wasted words. It's appropriately sized for the tool's complexity and front-loads the essential information about what the tool does.

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 creation/mutation tool with no annotations, no output schema, and incomplete parameter documentation, the description is inadequate. It doesn't address what happens after creation, what permissions are needed, how to handle errors, or how this differs from other channel creation tools. The description leaves too many contextual gaps for effective tool usage.

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 50% (2 of 4 parameters have descriptions). The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain what 'guild_id' represents, what format 'name' should follow, or provide examples. With partial schema coverage, the description doesn't compensate for the undocumented parameters, resulting in adequate but incomplete parameter documentation.

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 resource ('new forum channel in a guild'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'discord_create_channel' or 'discord_create_thread', which creates some ambiguity about when to use this specific forum creation tool versus other channel creation tools.

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. With sibling tools like 'discord_create_channel' and 'discord_create_thread' available, there's no indication of when a forum channel is appropriate versus other channel types, nor any mention of prerequisites or permissions required for this operation.

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