MCP-Discord

discord_create_forum_channel

Create a forum channel in a Discord server, optionally under a specific category.

Instructions

Creates a new forum channel in a Discord server, optionally under a category

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": {
      "guildId": "<guildId>",
      "name": "<name>"
    },
    "name": "discord_create_forum_channel"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`topic`	No	The forum channel guidelines/description
`guildId`	Yes
`categoryId`	No	The ID of the parent category to create the channel under

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.0Sep 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are present, so the description must convey behavior on its own. It states that the tool 'creates' a resource (implying mutation) but does not mention permissions, rate limits, side effects, or potential errors. It is not misleading, but it is minimal.

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, clear sentence with no extraneous information. It is efficiently structured and directly states the tool's purpose without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides enough context for a basic call, including the optional category placement. However, it omits information about return values, error handling, or required permissions, which would be useful for a complete understanding. Given the simplicity of the operation, it remains sufficient for most use cases.

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?

The schema provides descriptions for only two of the four parameters (topic and categoryId); guildId and name have no descriptions. The tool description itself does not clarify any parameters. Since half the parameters are undocumented, the semantic coverage is incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('creates') and the specific resource ('a new forum channel'), with an optional modifier ('optionally under a category'). It unambiguously distinguishes this tool from sibling channel-creation tools like create_text_channel and create_voice_channel.

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?

The description does not explicitly mention when to use this tool over alternatives, though the tool name and description make the primary use case obvious. It lacks guidance on conditions that would favor this tool versus others, such as creating a text or voice channel instead.

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

Deploy Server