Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_edit_channel

Idempotent

Update a Discord channel's name, topic, slowmode, or NSFW flag. Only provided fields change; topic and slowmode apply to text channels. Requires Manage Channels permission.

Instructions

Update a channel's name, topic, slowmode, or NSFW flag. Only provided fields change; topic and slowmode apply to text channels only. Requires the Manage Channels permission. Returns a confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew channel name (max 100 characters).
nsfwNoMark (true) or unmark (false) the channel as age-restricted (NSFW).
topicNoNew topic/description (text channels only).
slowmodeNoPer-user message cooldown in seconds, 0–21600. 0 disables slowmode.
channel_idYesID (snowflake) of the channel to edit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / slowmode / maximum
      Added value: +21600
    • addedInput schema / properties / slowmode / minimum
      Added value: +0
    • changedInput schema / properties / slowmode / type
      Previous value: -"number"New value: +"integer"
  3. Changed5 schema fields changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the channel to edit."
    • addedInput schema / properties / name / description
      Added value: +"New channel name (max 100 characters)."
    • changedInput schema / properties / nsfw / description
      Previous value: -"Mark channel as NSFW."New value: +"Mark (true) or unmark (false) the channel as age-restricted (NSFW)."
    • changedInput schema / properties / slowmode / description
      Previous value: -"Slowmode in seconds (0 to disable)."New value: +"Per-user message cooldown in seconds, 0–21600. 0 disables slowmode."
    • addedInput schema / properties / topic / description
      Added value: +"New topic/description (text channels only)."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The description adds meaningful behavioral detail beyond the annotations: partial-update semantics, text-channel-only restrictions for topic and slowmode, permission requirements, and a confirmation response. These are not visible in the annotations or schema and are especially valuable for a mutating tool.

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?

Three short sentences with no filler. The main purpose and editable fields are front-loaded, followed by the partial-update caveat, permission requirement, and return behavior. Every sentence earns its place.

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

Completeness5/5

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

For a moderately complex edit tool with full schema coverage and no output schema, the description covers the editable fields, constraints, permission, partial-update semantics, and return value. Nothing essential for correct invocation 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 100%, so the baseline is 3. The description adds value by explaining cross-parameter behavior ('Only provided fields change') and the text-channel-only constraint for topic and slowmode, which the schema does not convey.

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 names a specific verb ('Update') and resource ('a channel'), then enumerates exactly which fields are editable: name, topic, slowmode, or NSFW flag. This clearly distinguishes it from sibling tools like move_channel, set_channel_position, and delete_channel.

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?

The description makes the usage context clear: use it to update channel settings, only provided fields change, and topic/slowmode are text-channel-only. It also states the Manage Channels permission requirement. It does not explicitly name alternative sibling tools, but the field list effectively implies when this tool is appropriate.

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