Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_channel_permission

Allow or deny permissions for a role or member on a Discord channel using permission names, and lock channels by denying SEND_MESSAGES for @everyone.

Instructions

Allow/deny permissions for a role or member on a channel using names (e.g. allow ["VIEW_CHANNEL"], deny ["SEND_MESSAGES"]). Lock a channel: deny SEND_MESSAGES for @everyone (role id = server 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>",
      "target_id": "<target_id>",
      "target_type": "<target_type>"
    },
    "name": "set_channel_permission"
  }
}

Input Schema

NameRequiredDescriptionDefault
denyNo
allowNo
reasonNo
target_idYesRole ID (server ID = @everyone) or user ID
channel_idYes
target_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds real value beyond them: permissions are supplied as name lists, and the non-obvious convention that role id = server id targets @everyone. Gaps remain on whether existing overrides are merged or replaced, and on required permissions/auth.

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?

Two dense sentences with the core operation front-loaded and the lock recipe as a follow-up example; nothing is padding. The bracketed inline examples are slightly terse but readable.

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 mutation tool with no output schema and sparse schema descriptions, the definition covers the primary operation and the @everyone edge case. It omits merge-vs-overwrite behavior on existing permission overwrites, the reason parameter's purpose, and any return/confirmation detail, which an agent would need to act confidently.

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 17% (only target_id is documented), so the description must compensate, and it does partially: it clarifies allow/deny as lists of permission names and explains the @everyone case for target_id. It says nothing about reason, channel_id, or the role/member enum semantics, so compensation is incomplete.

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?

"Allow/deny permissions for a role or member on a channel" is a specific verb plus resource with scope (role vs member), and the example permission names make the operation concrete. It stops short of naming delete_channel_permission as the counterpart for removing overrides, so the agent gets no explicit sibling differentiation.

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 "Lock a channel" recipe shows one concrete scenario and the @everyone convention, which is genuinely actionable usage guidance. However, there is no when-not guidance and no mention that delete_channel_permission is the tool for clearing an override, leaving the alternative unstated.

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