discord-mcp

roles_modify

Idempotent

Update a Discord role's name, color, permissions, mentionability, hoist, or icon. Pass only fields to change; returns updated role details.

Instructions

Purpose: Update a role's properties. Pass only fields you want to change.

When to use:

Rename, recolor, change permissions, toggle mentionability/hoist, set role icon.

When NOT to use:

Reorder roles → use roles_modify_positions.
Delete → use roles_delete.

permissions is a base-10 STRING (Discord permission bitfield).

Returns: {id, name, color, position, permissions, mentionable, hoist}.

Input Schema

TableJSON Schema

Name	Required	Description
`icon`	No
`name`	No
`color`	No
`hoist`	No
`role_id`	Yes	Role to modify
`guild_id`	Yes	Guild containing the role
`mentionable`	No
`permissions`	No	Permission bitfield as base-10 string
`audit_reason`	No	Reason recorded in audit log (X-Audit-Log-Reason header)
`unicode_emoji`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.28.0Sep 15, 2026

removedInput schema / properties / hoist / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / hoist / type

Added value: +[
+  "boolean",
+  "null"
+]

removedInput schema / properties / icon / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / icon / type

Added value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / mentionable / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / mentionable / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedInput schema / properties / unicode_emoji / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / unicode_emoji / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedv0.22.0Aug 14, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The description adds partial-update semantics ('Pass only fields you want to change') and lists the return fields, complementing the annotations. It does not contradict readOnlyHint, destructiveHint, or idempotentHint, though it omits permission prerequisites and rate-limit context.

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 bold headings and bullet lists, front-loading the purpose and then giving usage boundaries. Every sentence adds value without unnecessary fluff.

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 10-parameter mutation tool with annotations and an output schema, the description is largely complete: it covers purpose, alternatives, field semantics, and return shape. It could still improve by explaining `unicode_emoji` and noting the required Manage Roles permission, but the core calling context is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents only 4 of 10 parameters, so the description must compensate. It maps use cases like rename, recolor, change permissions, toggle mentionability/hoist, and set role icon to the undocumented fields, and clarifies `permissions` as a base-10 string. However, `unicode_emoji` remains under-specified.

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?

States a specific verb and resource: 'Update a role's properties.' The scope is clear, and the description explicitly distinguishes this from reordering and deletion by naming the sibling tools.

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?

Provides explicit 'When to use' and 'When NOT to use' sections, naming alternatives `roles_modify_positions` and `roles_delete`. This leaves no ambiguity about when this tool should be selected.

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

Deploy Server