discord-mcp

Create channel (admin)

discord_admin_create_channel

Creates Discord categories, text, forum, announcement, or voice channels and configures topics, tags, sorting, role visibility, and audit-log reasons.

Instructions

Create a category, text, forum, announcement or voice channel. For forums you can set tags, require a tag, default sort, and the post guidelines (topic). private_to_roles makes it visible only to those roles (and this bot).

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`tags`	No	Forum only: tag names
`type`	No		text
`topic`	No	Channel topic, or a forum's post guidelines
`reason`	No	Reason, recorded in Discord's audit log
`category_id`	No	Put it in this category
`require_tag`	No	Forum only: posts must have a tag
`default_sort`	No	Forum only
`private_to_roles`	No	Role names or IDs that can see it; everyone else can't

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. Beyond that, the description discloses forum-specific behavior (tags, require_tag, default sort, post guidelines) and the non-obvious visibility semantic that private_to_roles also grants access to 'this bot'. It still omits permission prerequisites and any rate-limit or error behavior for a write operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and channel types, followed by option-specific detail. Nearly every clause carries information; the only mild redundancy is restating forum options the schema already describes.

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

Completeness3/5

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

For a 9-parameter mutation tool with no output schema, the description covers channel types and forum/visibility behavior but leaves gaps on authorization requirements, whether category_id must reference an existing category, and what the call returns. Adequate but not complete for the tool's complexity.

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 78%, so the schema already documents most parameters, including topic-as-post-guidelines, tags, require_tag, default_sort, and reason. The description mainly echoes those forum options, adding real meaning only for private_to_roles (visibility is restricted to those roles plus the bot). Baseline 3 is appropriate.

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 first sentence gives a specific verb ('Create') and enumerates the exact resource variants supported (category, text, forum, announcement, voice), which lets an agent match intent quickly. It does not explicitly contrast with nearby siblings such as discord_create_thread or discord_admin_setup_category, so differentiation is left implicit.

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?

Usage is implied by the option groupings: 'For forums you can set tags...' and the private_to_roles visibility note indicate when those options apply. There is no explicit when-not-to-use guidance, no mention of required permissions, and no pointer to discord_admin_edit_channel for modifying an existing channel or discord_create_thread for threads.

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

Deploy Server