Skip to main content
Glama
Sign In
Discord MCP

Discord MCP

by RestartFU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_channel

Destructive

Modify a Discord channel's name, topic, permissions, or thread metadata directly by supplying its ID and desired fields.

Instructions

Update channel name, topic, permissions, or thread metadata using Discord fields.

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>",
      "data": "<data>"
    },
    "name": "update_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
channel_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which already convey that changes are made. The description adds the word 'update', which aligns with those annotations but does not provide additional behavioral context, such as side effects or whether existing data is replaced or merged.

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?

The description is concise and directly to the point, containing no unnecessary words or repetition. It clearly communicates the essence of the tool in a single sentence.

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?

The tool is missing crucial context about the data parameter's structure and allowed fields. Without this, an agent would not know how to construct a valid request, and the behavior of the tool when updating permissions or metadata is not explained.

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?

The channel_id parameter is well-defined as a string, but the data parameter is an open object with no specified properties. The description mentions 'Discord fields' but does not enumerate them or explain what fields are accepted, leaving the parameter's meaning vague and under-specified.

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 clearly states the tool updates a channel with specific examples (name, topic, permissions, thread metadata) and uses the verb 'update', making its purpose explicit. However, it does not explicitly differentiate from sibling tools like 'create_channel' or 'update_member', though the resource is clear from the channel_id parameter.

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 does not provide any guidance on when to use this tool versus alternatives. Sibling tools like 'create_channel' or 'update_member' are not referenced, and there is no indication of prerequisites or conditions under which this tool should be chosen.

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