discord-mcp

Create role (admin)

discord_admin_create_role

Create a Discord role with a name, color, and named permissions. Use it to define member access levels, optionally hoisting or making roles mentionable, with an audit log reason.

Instructions

Create a role with named permissions (see discord_admin_set_permissions for names). The bot can only manage roles below its highest role.

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": "discord_admin_create_role"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`color`	No
`hoist`	No	Show members separately in the member list
`reason`	No	Reason, recorded in Discord's audit log
`mentionable`	No
`permissions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation. The description adds a real constraint beyond the schema: the bot can only manage roles below its highest role, which tells the agent when a call will fail. It doesn't mention return payload or audit-log implications, but the hierarchy caveat is substantive 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?

Two short sentences with zero filler, and the permission-name pointer is front-loaded alongside the core action. Nothing is redundant with the title.

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 six-parameter mutation with no output schema, the definition covers the essential permission-naming path and the hierarchy restriction, but leaves color formatting, hoist/mentionable effects, and the audit-log reason unexplained. Adequate but with clear gaps.

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 33%, so the description must compensate; it partially does by telling the agent that the permissions array takes permission names discoverable via discord_admin_set_permissions. The color, hoist, and mentionable parameters get no explanation, and the reason/audit-log linkage is left entirely to the schema's own field description.

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 gives a specific verb and resource ('Create a role') and adds a scope detail about named permissions. It points to discord_admin_set_permissions for permission names, though it doesn't explicitly distinguish itself from sibling creation helpers like discord_admin_setup_roles or discord_admin_bulk_roles.

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 redirects the agent to discord_admin_set_permissions for permission naming, which is genuine routing guidance for one parameter. However, there is no explicit when-to-use versus discord_admin_edit_role or when to prefer setup_roles, so usage is only partially implied.

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

Deploy Server