Skip to main content
Glama

Edit channel (admin)

discord_admin_edit_channel
Destructive

Update a Discord channel's name, category, position, topic, forum tags, default sort, or slowmode in one call to keep server structure and posting rules current.

Instructions

Rename, move, reorder or change a channel's topic / forum post guidelines, forum tags (replaces the full tag list; existing tags with the same name are kept so posts keep them), require-tag, default sort or slowmode. category_id: "none" removes it from its 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": {
      "channel_id": "<channel_id>"
    },
    "name": "discord_admin_edit_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
tagsNo
topicNo
reasonNoReason, recorded in Discord's audit log
positionNo
channel_idYesChannel, forum or category ID
category_idNo
require_tagNo
default_sortNo
slowmode_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds genuinely non-obvious behavior beyond them: "tags ... replaces the full tag list; existing tags with the same name are kept so posts keep them" and "category_id: \"none\" removes it from its category." That replace-not-merge semantics is exactly the kind of destructive side effect an agent needs to know before calling; what's still missing is permission requirements and whether omitted fields are left untouched.

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?

A single dense sentence with the editable surface front-loaded and clarifications parenthesized, so it is easy to scan. It is slightly run-on and the tags parenthetical is long, but every clause carries information.

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 destructive 10-parameter mutation with no output schema, the description covers the field semantics well but omits prerequisite admin permissions, whether the call is partial-update, and any note about Discord's tight channel-edit rate limits. Those are meaningful gaps for an agent planning a multi-field edit, though annotations plus this text cover the basics.

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?

With only 20% schema description coverage across 10 parameters, the description carries most of the semantic load and does so for name, position, topic, tags, require_tag, default_sort, slowmode and category_id — including the critical tags-replacement and "none" sentinel behavior that the schema only hints at. Only reason and channel_id are left to the schema, which already documents them, so the coverage gap is largely compensated.

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?

Opens with specific verbs tied to the resource ("Rename, move, reorder or change a channel's topic ... slowmode") and enumerates the exact editable properties, so an agent knows precisely what the tool mutates. It does not explicitly contrast itself with siblings like discord_admin_reorder or discord_admin_setup_category, which an agent could plausibly confuse with position/category changes.

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 field list — use this to modify an existing channel rather than create/clone/delete one — but there is no explicit when-to-use/when-not statement, no mention that the caller needs admin permissions, and no pointer to alternatives for pure reordering.

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