Skip to main content
Glama
Discord Vencord MCP Bridge

Discord Vencord MCP Bridge

by clawdecode

discord_modify_channel

Update an existing Discord channel's name, topic, NSFW flag, parent category, or slowmode with targeted changes.

Instructions

Modify an existing channel (name, topic, NSFW, parent category, slowmode).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discord_modify_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew channel name.
nsfwNoSet NSFW flag.
topicNoNew channel topic.
parent_idNoParent category ID.
channel_idNoTarget channel ID (defaults to active channel).
rate_limit_per_userNoSlowmode in seconds (0-21600).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether omitted fields are left unchanged, whether the operation is reversible, what permissions are required, or what happens to a channel when moved to a new parent category.

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 front-loaded sentence that gets to the point without padding. It is appropriately sized for a simple modify tool, though it could have spent its brevity budget on mutation semantics rather than restating the field list.

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 mutation tool with no annotations and no output schema, the description should explain partial-update behavior, permission requirements, and reversibility. None of that is present, leaving an agent to guess at the consequences of a write operation.

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 100%, so the schema already documents every parameter including slowmode's 0-21600 range and the active-channel default. The description's parenthetical list largely restates the schema fields, adding little beyond what is already structured.

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 gives a specific verb+resource ("Modify an existing channel") and enumerates the editable fields, which clearly separates it from discord_create_channel and discord_delete_channel. It stops short of explicitly naming those siblings as alternatives, but the purpose is unambiguous.

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?

There is no guidance on when to use this tool versus discord_create_channel or discord_delete_channel, nor any prerequisites such as needing Manage Channels permission. The word "existing" implies the channel must already exist, but that is the only contextual cue.

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