discord-mcp

Edit role (admin)

discord_admin_edit_role

Destructive

Rename a Discord role or update its color, display settings, or permissions; add or remove individual permissions and record changes in the audit log.

Instructions

Rename a role, or change its colour, display or permissions. permissions replaces the whole set; use add_permissions / remove_permissions to change a few.

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": {
      "role": "<role>"
    },
    "name": "discord_admin_edit_role"
  }
}

Input Schema

Name	Required	Description
`name`	No
`role`	Yes	Role name or ID
`color`	No
`hoist`	No
`reason`	No	Reason, recorded in Discord's audit log
`mentionable`	No
`permissions`	No
`add_permissions`	No
`remove_permissions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description usefully pins down the specific destructive behavior: 'permissions replaces the whole set', which is the main way an agent could silently wipe data. It adds nothing about required permissions, reversibility, or rate limits, so it is a solid but partial supplement.

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?

Two short sentences: the capability list comes first, then the one non-obvious routing rule. No redundancy or filler, and nothing important is buried.

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 9-parameter destructive mutation with no output schema, the description covers the one thing most likely to cause damage (whole-set permission replacement). Missing details are secondary: hoist/mentionable semantics and the Manage Roles permission prerequisite.

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?

With schema coverage at 22% for 9 parameters, the description must compensate, and it does clarify the highest-risk trio (permissions / add_permissions / remove_permissions). However, 'display' loosely gestures at hoist/mentionable without mapping to either, and color, reason, and the role's name-or-ID acceptance are left entirely to the schema.

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 concrete verb ('rename', 'change') plus the resource ('a role') and enumerates the editable facets: colour, display, permissions. The action is clearly an edit of an existing role, which distinguishes it from create_role/delete_role, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Gives an explicit parameter-level routing rule: use 'permissions' to replace the whole set, or add_permissions / remove_permissions to change a few. It does not address when to prefer this over discord_admin_set_permissions or set_member_roles, so it stops short of full alternative guidance.

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

Deploy Server