Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_delete_permission_overwrite

Removes a permission overwrite for a role or member on one Discord channel, restoring inherited channel permissions.

Instructions

Remove the permission overwrite for a role or member on one channel.

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": {
      "guildId": "<guildId>",
      "channelId": "<channelId>",
      "targetId": "<targetId>"
    },
    "name": "discord_delete_permission_overwrite"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
guildIdYesDiscord id (snowflake)
targetIdYes
channelIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and it delivers little: it does not say this is an irreversible mutation, what permissions are required (Manage Roles / Manage Channel), or whether removing an overwrite reverts the target to category-synced permissions. The one useful hint is that the target may be either a role or a member.

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 well-formed sentence with the resource and scope front-loaded and no filler. It is efficient, though the same length budget could have been spent on a behavioral detail instead of nothing.

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 destructive mutation with no annotations, no output schema, and 4 parameters at 25% schema coverage, the description is too thin — it omits required permissions, irreversibility, the fate of the target's effective permissions, and the `reason` parameter. An agent could call it, but without understanding the consequences.

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 coverage is only 25% (only guildId carries a description; channelId and targetId are bare $refs), so the description needs to compensate. It does add meaning by clarifying that targetId is a role-or-member id and channelId scopes to "one channel", but it says nothing about the optional `reason` parameter (presumably an audit-log reason) or the required-id formats.

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 ("Remove") plus the exact resource ("permission overwrite") and scopes it to "a role or member on one channel". This cleanly separates it from discord_edit_permission_overwrite and discord_list_permission_overwrites without naming them, though it never explicitly names an alternative.

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 when-to-use / when-not-to-use guidance and no mention of the edit or list siblings, which are the natural alternatives for the same resource. Usage is only inferable from the verb itself.

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