Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_channel

Edit a Discord channel, thread, or group DM to update its name, topic, slowmode, NSFW status, category, permissions, bitrate, archive/lock state, or icon.

Instructions

Edit a channel, thread or group DM: name, topic, slowmode, NSFW, category, permissions, bitrate, thread archive/lock, group DM icon… [PATCH /channels/{channel_id}]

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": "modify_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoGroup DM icon: local file path, URL or data: URI
nameNoName
nsfwNo
typeNoChange type (only text 0 <-> announcement 5)
flagsNoFlags bitfield
ownerNoGroup DM: new owner user ID
topicNo
lockedNoThread: locked
reasonNoReason (shown in the audit log)
bitrateNo
archivedNoThread: archived
positionNo
invitableNoPrivate thread: members can invite
parent_idNo
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
rtc_regionNo
user_limitNo
applied_tagsNoForum post: tag IDs
available_tagsNoForum tags: [{name, moderated?, emoji_id?, emoji_name?}]
default_sort_orderNo
video_quality_modeNo
rate_limit_per_userNo
default_forum_layoutNoForum layout: 0 not set, 1 list, 2 gallery
auto_archive_durationNoThread: auto-archive minutes
permission_overwritesNo
default_reaction_emojiNo
default_auto_archive_durationNo
default_thread_rate_limit_per_userNodefault thread rate limit per user

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and readOnlyHint=false; the description adds the PATCH endpoint, which usefully signals partial-update semantics (only supplied fields change). It says nothing about the MANAGE_CHANNELS-style permissions required, whether changes are audited, or rate limits, so for a 28-parameter mutation the behavioral disclosure is thin beyond annotations.

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?

A single front-loaded sentence plus an endpoint tag; the field enumeration is dense but every element conveys a distinct editable surface. No filler.

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?

With 28 parameters and no output schema, an overview of editable fields is helpful, but the description does not cover the required channel_id, permission prerequisites, or which fields are valid for which channel type (beyond scattered hints). Adequate but with clear gaps for a mutation of this breadth.

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 54%, so some parameters are self-documented, but roughly half are not. The description names a subset of fields (name, topic, slowmode, NSFW, bitrate, archive/lock, icon) without adding constraint, default, or format meaning, and omits many parameters such as owner, position, rtc_region, user_limit, forum tags, and type.

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?

States a specific verb and resource ("Edit a channel, thread or group DM") and enumerates the editable field families, so an agent knows this is the broad partial-update tool rather than a specialized one. It loses a point because it lists "permissions" among the fields even though siblings modify_channel_permissions and set_channel_permission exist, leaving the boundary between them unstated.

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 only implied by the list of applicable targets (thread archive/lock, group DM icon), which hints at when each field applies but never states when to pick this tool over the permission-specific siblings. No prerequisites, no when-not-to-use, no mention of required permissions.

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