Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_channel_permissions

Set or update a channel permission overwrite for a role or member by specifying allowed and denied permissions, with an optional audit log reason.

Instructions

Set a permission overwrite on a channel for a role or member (type 0 = role, 1 = member). allow/deny accept names like ["SEND_MESSAGES"]. [PUT /channels/{channel_id}/permissions/{overwrite_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>",
      "overwrite_id": "<overwrite_id>",
      "type": "<type>"
    },
    "name": "modify_channel_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
denyNoDenied permissions: bitfield string or names
typeYes0 = role, 1 = member
allowNoAllowed permissions: bitfield string or names
reasonNoReason (shown in the audit log)
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
overwrite_idYesRole ID or user ID that the permission overwrite targets

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 set readOnlyHint=false, destructiveHint=false and openWorldHint=true. The description adds the value format for allow/deny (names like ["SEND_MESSAGES"]) and the underlying PUT endpoint, but omits the most important risk detail: whether this replaces the existing overwrite entirely or merges with it, and what permission (e.g. MANAGE_CHANNELS) the caller needs.

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 delivers the operation, target types and value format, with the endpoint as a compact trailing tag. Nothing is wasted and nothing important is buried.

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?

For a 6-parameter permission-mutating tool with no output schema, the definition covers purpose and value syntax but leaves out auth requirements, replace-vs-merge behavior, and what is returned on success. Adequate to call correctly, but not complete for a mutation with permission implications.

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 every parameter is already documented in the schema, including 'type: 0 = role, 1 = member' and 'allow/deny: bitfield string or names'. The description largely restates that schema content, so baseline 3 is appropriate.

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 ('Set a permission overwrite on a channel') plus the target types (role or member), which lets an agent distinguish it from sibling tools like delete_channel_permission or modify_application_command_permissions. It stops short of naming an alternative explicitly, but the operation 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 Guidelines3/5

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

The parenthetical 'type 0 = role, 1 = member' implicitly guides parameter selection, but there is no explicit when-to-use/when-not or reference to the delete/get permission siblings. An agent must infer that this creates-or-replaces an overwrite while delete_channel_permission removes it.

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