Discord MCP - Discord server management MCP for AI agents

Clear channel permissions

clear_channel_permissions

Removes a role's or member's channel permission overwrite so access follows roles and other overwrites, with confirmation for sensitive removals.

Instructions

Remove a role's or member's permission overwrite from a channel, so their permissions there come from their roles and the other overwrites. On a category, Discord also makes the same change in every channel inside whose permissions match the category's exactly (synced), as the Discord app does; the result names them. To keep such a channel as it is, change that channel first, which stops it matching. get_channel_permissions says whether a channel is synced. Removing one that keeps someone out (a private channel's denial for @everyone, say) needs confirming, as does one whose removal gives moderator or admin powers (such as banning, kicking, or timing out members, deleting other people's messages, or managing the server, roles, or channels): the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

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": "<channel>",
      "target": "<target>"
    },
    "name": "clear_channel_permissions"
  }
}

Input Schema

Name	Required	Description
`guild`	No	Guild (server) name or ID. Omit to use the default guild.
`target`	Yes	Role or member name or ID.
`channel`	Yes	Channel name or ID.
`confirm_token`	No	The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.4.2Nov 12, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / confirm_token

Added value: +{
+  "description": "The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.",
+  "type": "string"
+}

Changed1 schema field changedv1.3.0Aug 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.0.2Jun 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well past the annotations: it discloses the synced-category propagation side effect, that the result names affected channels, and the full two-step confirmation protocol (first call changes nothing and returns a preview plus confirm_token; repeating with the token applies it). The specific risk classes that trigger confirmation — private-channel denials and granting moderator/admin powers — are spelled out, which the readOnlyHint/destructiveHint pair alone cannot convey.

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?

Front-loaded with purpose and scoping, then the cascade caveat, then the confirmation rules — a sensible order. It is a single dense paragraph with a couple of long nested clauses (the moderator/admin powers list) that would scan better as a short list, but no sentence is filler.

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

Completeness5/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 output schema, it covers the side effects, the two-phase confirmation, the return content (names of affected channels), and the precondition for changing a synced channel. An agent has everything needed to call it correctly and to handle the preview/confirm loop.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline would be 3; the description adds real meaning by explaining the confirm_token workflow and tying the channel parameter to sync behavior. It does not, however, add anything about guild or target resolution (name vs ID, what happens if a member and role share a name).

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?

States a precise verb and object: "Remove a role's or member's permission overwrite from a channel," and immediately clarifies the consequence (permissions then come from roles and other overwrites). This is clearly distinguishable from the sibling set_channel_permissions (which sets an overwrite) and get_channel_permissions (referenced explicitly as the read-side check).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly tells the agent when the category-sync cascade applies and how to avoid it ("To keep such a channel as it is, change that channel first"), points to get_channel_permissions to check sync state, and states exactly which removals require confirmation. The alternative action and the conditions that select it are both named.

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

Deploy Server