Skip to main content
Glama
Sign In
MCP-Discord

MCP-Discord

by barryyip0625
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_remove_channel_permissions

Remove all permission overrides for a specified role or user on a given channel or category.

Instructions

Removes all permission overrides for a role or user on a channel or category

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": {
      "channelId": "<channelId>",
      "roleId": "<roleId>"
    },
    "name": "discord_remove_channel_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
roleIdYesRole or user ID to remove overrides for
channelIdYesChannel or category ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full transparency burden. It states the core behavior clearly but does not mention side effects such as reverting to inherited/default permissions, required permissions, or irreversibility.

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 a single concise sentence with no redundant information, fluff, or unnecessary detail.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple mutation tool with no output schema, the description provides sufficient context about what action is performed. It could be slightly more complete by mentioning the effect on inherited permissions, but the core context is covered.

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 67%, above the 50% threshold, so baseline is 3. The description does not add any parameter meaning beyond the existing schema descriptions for channelId and roleId, and reason remains undocumented.

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 uses a specific verb 'Removes' and clearly identifies the resource and scope: all permission overrides for a role or user on a channel or category. It is easily distinguishable from the sibling tool discord_set_channel_permissions.

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 description implies when to use the tool (when all overrides need to be removed) but does not explicitly contrast it with alternatives like discord_set_channel_permissions or provide guidance on when not to use 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