discord-mcp

channels_delete_permissions

Idempotent

Remove a permission overwrite from a channel to revert it to inheriting role or category defaults. Clears a specific role or user override.

Instructions

Purpose: Remove a permission overwrite from a channel.

When to use:

Revert a channel back to inheriting role/category defaults.

When NOT to use:

Changing allow/deny bits → use channels_modify_permissions.

Returns: {deleted, channel_id, overwrite_id}. Removing an overwrite that does not exist is treated as success by Discord.

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

Input Schema

Name	Required	Description
`channel_id`	Yes	Channel whose overwrite is being removed
`audit_reason`	No	Reason recorded in audit log (X-Audit-Log-Reason header)
`overwrite_id`	Yes	Role ID or user ID whose overwrite to remove

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.22.0Aug 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description adds behavioral context beyond the annotations: it explains the return format (`{deleted, channel_id, overwrite_id}`) and the idempotent behavior of treating non-existent overwrites as success, which aligns with `idempotentHint=true`. It does not mention auth requirements, but the annotations already cover safety (`readOnlyHint=false`, `destructiveHint=false`). No contradiction found.

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 well-structured with clear sections (Purpose, When to use, When NOT to use, Returns) and every sentence provides necessary information without redundancy. It is concise and front-loaded with the main purpose.

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 relatively simple delete operation, the description covers purpose, usage boundaries, return behavior, and edge-case handling. The input schema is fully documented, and the output schema exists. The description is complete enough for an agent to select and invoke the tool correctly.

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 baseline is 3. The description does not add significant new meaning to the parameters beyond the schema, though the return format indirectly clarifies `channel_id` and `overwrite_id`. This is acceptable given the schema's completeness.

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?

The description clearly states the action: 'Remove a permission overwrite from a channel.' It uses a specific verb and resource, and the 'When NOT to use' section explicitly distinguishes it from the sibling tool `channels_modify_permissions`, so there is no ambiguity about its purpose.

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?

The description provides explicit when-to-use guidance ('Revert a channel back to inheriting role/category defaults') and when-not-to-use guidance ('Changing allow/deny bits → use `channels_modify_permissions`'), including a named alternative. This fully clarifies usage context.

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

Deploy Server