Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_edit_channel

Modify a Discord channel by renaming it or updating its topic, slowmode, NSFW flag, category, or position. Use it to enforce server structure and channel settings without manual UI changes.

Instructions

Rename a channel, change its topic, slowmode, NSFW flag, category or position.

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": {
      "guildId": "<guildId>",
      "channelId": "<channelId>"
    },
    "name": "discord_edit_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
nsfwNo
topicNo
reasonNo
guildIdYesDiscord id (snowflake)
parentIdNoMove to this category, null to remove
positionNo
channelIdYes
slowmodeSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation tool. It does not disclose permission requirements, partial-update semantics, audit-log behavior for the reason field, reversibility, or what the tool returns after editing.

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 definition is a single efficient sentence with the resource and editable attributes front-loaded. There is no wasted wording, though the terse list format leaves no room for behavioral or usage detail.

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?

For a 9-parameter mutation tool with no annotations, no output schema, and low schema description coverage, the description is too thin. It should at minimum explain partial-update behavior, required IDs, permission needs, and the purpose of the reason field.

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 only 22%, so the description must compensate; it usefully maps most editable fields (name, topic, slowmode, NSFW, category, position) to their parameters. However, it omits the required guildId/channelId semantics and the reason parameter, leaving meaningful gaps at this low coverage level.

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?

The description uses a clear verb ('Rename') plus resource ('channel') and enumerates the editable attributes, so the tool's purpose is immediately understandable. It does not explicitly differentiate from siblings such as discord_set_channel_position, which overlaps with the position-editing capability.

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?

The description lists what can be changed but provides no guidance on when to use this tool versus alternatives, nor any prerequisites such as required permissions. An agent must infer all usage conditions from the schema and sibling names.

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