Discord MCP - Discord server management MCP for AI agents

Create role

create_role

Create a Discord role from a preset or explicit permission list, optionally add colors or icons, and preview the result with dry run.

Instructions

Create a role from a vetted preset (none, member, moderator, admin) and/or an explicit list of permission names. Administrator is never granted by a preset; it must be spelled out explicitly. Can start with a gradient or holographic color and an icon where the server has those features. Supports dry_run.

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

Input Schema

Name	Required	Description
`name`	Yes	Role name.
`color`	No	Hex color like #00b0f4.
`guild`	No	Guild (server) name or ID. Omit to use the default guild.
`hoist`	No	Show members separately in the sidebar.
`preset`	No	Vetted permission bundle. Default none.
`dry_run`	No	Preview without creating.
`icon_url`	No	Public URL of a small image (png, jpeg, webp; 256 KB) shown beside members' names, or none to remove. Needs boost level 2.
`icon_emoji`	No	A standard emoji shown beside members' names instead of an image, or none to remove. Needs boost level 2.
`holographic`	No	Discord's holographic style, which uses its own three colors; false for a solid color. Needs the Enhanced Role Colors server feature.
`mentionable`	No
`permissions`	No	Extra permission names, like manage_messages or ban_members.
`secondary_color`	No	A second hex color, so the role name shows a gradient from color to this one; none for a solid color. Needs the Enhanced Role Colors server feature.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.4.2Nov 12, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / holographic

Added value: +{
+  "description": "Discord's holographic style, which uses its own three colors; false for a solid color. Needs the Enhanced Role Colors server feature.",
+  "type": "boolean"
+}

addedInput schema / properties / icon_emoji

Added value: +{
+  "description": "A standard emoji shown beside members' names instead of an image, or none to remove. Needs boost level 2.",
+  "type": "string"
+}

addedInput schema / properties / icon_url

Added value: +{
+  "description": "Public URL of a small image (png, jpeg, webp; 256 KB) shown beside members' names, or none to remove. Needs boost level 2.",
+  "type": "string"
+}

addedInput schema / properties / secondary_color

Added value: +{
+  "description": "A second hex color, so the role name shows a gradient from color to this one; none for a solid color. Needs the Enhanced Role Colors server feature.",
+  "type": "string"
+}

Changed1 schema field changedv1.3.0Aug 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.0.2Jun 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses a genuinely important behavioral rule: the admin preset never grants Administrator and it must be named explicitly. It also flags server-feature dependencies for icon and holographic styling. It stops short of saying what happens on name collisions or missing permissions.

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?

Four tight sentences, front-loaded with the permission model and the Administrator caveat. The third sentence ('gradient or holographic color and an icon where the server has those features') is vague and largely duplicates schema detail, so it does not fully earn its place.

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 12-parameter mutation tool with no output schema, the definition covers the highest-risk semantics (Administrator escalation, presets, dry_run, feature requirements). It omits error/return behavior, but the rich schema carries the per-parameter burden.

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 92%, so the baseline is 3. The description restates the preset enum and clarifies that permissions are additive extras, but the feature gating it mentions (boost level 2, Enhanced Role Colors) is already present in the schema descriptions for icon_url, icon_emoji, holographic, and secondary_color.

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?

The description states a specific verb and resource ('Create a role') and immediately names the two ways to specify permissions (a preset bundle or an explicit permission list). The 'Create' verb naturally separates it from update_role/clone_role/delete_role in the sibling set, 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 Guidelines3/5

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

It explains what can be supplied but gives no explicit when-to-use / when-not-to-use guidance and never points to an alternative such as clone_role when an existing role should be copied. The dry_run mention implies a preview workflow but does not spell out when to prefer it.

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

Deploy Server