Skip to main content
Glama
OrygnsCode

Omnicord - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create channel

create_channel

Create a text, voice, forum, stage, announcement, or category channel, optionally inside a category, and optionally private or read-only from the start.

Instructions

Create a text, voice, forum, stage, announcement, or category channel, optionally inside a category, and optionally private or read-only from the start. private_to, read_only and posting_roles compile to permission overwrites and are applied in the same call, so a private channel is one request rather than a create followed by set_channel_permissions. Use set_channel_permissions for anything finer. Supports dry_run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesChannel name.
nsfwNo
typeNoChannel type. Default text.
guildNoGuild (server) name or ID. Omit to use the default guild.
topicNoChannel topic, for text-like channels.
dry_runNoPreview without creating.
categoryNoCategory name or ID to place the channel under.
read_onlyNoDeny sending to everyone, for rules and announcement channels.
private_toNoRole names that can see the channel. Everyone else is denied View Channel, and Connect too on voice, stage and category. Do not list @everyone.
posting_rolesNoRole names that may still post when read_only is set. Has no effect on its own.
slowmode_secondsNoPer-user message cooldown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.0
    • addedInput schema / properties / posting_roles
      Added value: +{
+  "description": "Role names that may still post when read_only is set. Has no effect on its own.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}
    • addedInput schema / properties / private_to
      Added value: +{
+  "description": "Role names that can see the channel. Everyone else is denied View Channel, and Connect too on voice, stage and category. Do not list @everyone.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}
    • addedInput schema / properties / read_only
      Added value: +{
+  "description": "Deny sending to everyone, for rules and announcement channels.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries most of the burden and delivers real value: private_to, read_only and posting_roles compile to permission overwrites and are applied in the same request, and dry_run is supported. It stops short of stating required permissions (e.g. Manage Channels) or uniqueness constraints on the name.

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?

Three sentences, front-loaded with the capability, then the permission-compilation behavior, then the routing note. The trailing 'Supports dry_run.' fragment is a slight appendage that largely restates the schema description, but nothing else is wasted.

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?

For an 11-parameter, one-required, no-output-schema mutation tool, the description covers channel types, placement, privacy/read-only semantics, permission compilation, the alternative tool, and dry_run. Minor gaps remain (permission prerequisites, whether the created channel is returned, and untouched parameters like slowmode_seconds/nsfw) but nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 91%, so the baseline is 3. The description exceeds that by explaining the cross-parameter interaction the schema does not state on its own: that private_to, read_only and posting_roles are compiled together into permission overwrites within a single call, and that posting_roles only matters when read_only is set.

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 first sentence states a specific verb (Create) plus the exact resource (channel) and enumerates all six creatable channel types, along with the optional category placement and privacy/read-only modifiers. An agent can distinguish this from update_channel, clone_channel or reorder_channels without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-not ('Use set_channel_permissions for anything finer') and a rationale for preferring this tool over a create-then-set-permissions sequence. It does not mention the closest functional overlap, clone_channel (also a channel-creating sibling), so the routing guidance is clear but not exhaustive.

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

Deploy Server

Other Tools