Skip to main content
Glama
Sys0xdbg

better-discord-mcp

by Sys0xdbg

discord_edit_channel

Edit a Discord channel or category by updating its name, topic, parent, position, slowmode, NSFW status, or voice settings like bitrate and user limit.

Instructions

Edit a channel/category (name, topic, parent/category, position, slowmode, nsfw, voice bitrate/limit).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
nsfwNo
topicNo
reasonNo
bitrateNo
parentIdNoMove under this category (empty string to remove)
positionNo
channelIdYes
userLimitNo
slowmodeSecondsNo
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It does not mention permissions requirements, that unspecified fields remain unchanged, or any side effects of editing channels/categories. The description is minimal and lacks important safety context for a mutation tool.

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?

The description is a single sentence that efficiently lists editable fields. However, it could be better organized (e.g., using bullet points) but it has no unnecessary words.

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

Completeness2/5

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

With 10 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the return value, error conditions, or that only specified fields are updated. Leaves significant gaps for the agent.

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

Parameters2/5

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

Schema description coverage is only 10% (only parentId has a description). The description lists parameters but does not add meaning beyond their names—e.g., 'slowmode' corresponds to slowmodeSeconds but no units, 'voice bitrate/limit' maps to bitrate and userLimit without clarification. It fails to compensate for the low schema coverage.

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 clearly states 'Edit a channel/category' and lists specific editable fields (name, topic, parent/category, position, slowmode, nsfw, voice bitrate/limit). This distinguishes it from sibling tools like discord_create_channel and discord_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 Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like discord_edit_guild or discord_edit_role. The description only states what it edits, not when it's appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sys0xdbg/better-discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server