discord-server-mcp

create_role

Creates a Discord role with a name, color, permissions, and display options. Use it to set up new roles for server members or bots, with an optional dry run to preview changes first.

Instructions

Create a role. Permission names: CreateInstantInvite, KickMembers, BanMembers, Administrator, ManageChannels, ManageGuild, AddReactions, ViewAuditLog, PrioritySpeaker, Stream, ViewChannel, SendMessages, SendTTSMessages, ManageMessages, EmbedLinks, AttachFiles, ReadMessageHistory, MentionEveryone, UseExternalEmojis, ViewGuildInsights, Connect, Speak, MuteMembers, DeafenMembers, MoveMembers, UseVAD, ChangeNickname, ManageNicknames, ManageRoles, ManageWebhooks, ManageGuildExpressions, UseApplicationCommands, RequestToSpeak, ManageEvents, ManageThreads, CreatePublicThreads, CreatePrivateThreads, UseExternalStickers, SendMessagesInThreads, UseEmbeddedActivities, ModerateMembers, ViewCreatorMonetizationAnalytics, UseSoundboard, CreateGuildExpressions, CreateEvents, UseExternalSounds, SendVoiceMessages, SendPolls, UseExternalApps, PinMessages.

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
`bot`	No	Use this bot (name or id) instead of choosing automatically
`name`	Yes
`color`	No
`reason`	No	Reason shown in the server's audit log
`server`	No	Server name or id. Optional when the bot is in one server or DISCORD_GUILD_ID is set.
`dry_run`	No	Show the requests that would be made without changing anything
`icon_emoji`	No	Unicode emoji shown next to names (needs boost level 2)
`icon_image`	No	Image path or URL (needs boost level 2)
`mentionable`	No
`permissions`	No	Default: none of its own (members still get what @everyone allows)
`shown_separately`	No	Show members with this role in their own group

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The only annotation is readOnlyHint=false, so the mutating nature is already declared; the description adds nothing about required permissions, role-hierarchy constraints, boost-level gating beyond what the schema notes, or what happens on partial failure. The permission name list adds real functional information but is closer to parameter semantics than behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is maximally front-loaded, but the permission block is an ungrouped 52-item run-on with no categories, no statement that these are the accepted values for the `permissions` array, and no indication of which are mutually exclusive or premium-gated. Every token is data rather than filler, yet the structure makes it hard to scan.

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 an 11-parameter mutation tool with no output schema, the description covers the hardest parameter but omits auth requirements, hierarchy rules, and the relationship between color/icon_emoji/icon_image and boost levels. An agent can attempt the call, but its chance of a first-try success with non-trivial permissions is only partly supported.

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?

Schema coverage is 73%, and the critical gap is the `permissions` array, whose items are untyped strings with no enum — the description supplies the entire valid name vocabulary (CreateInstantInvite ... PinMessages), which is the single most useful piece of information for calling this tool correctly. It adds little for the other ten parameters, whose meanings the schema already documents.

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 specific verb and resource ("Create a role"), which is enough for an agent to distinguish it from delete_role and edit_role in the sibling list. It does not explicitly name those alternatives or state the scope (server-level), so it stops short of full differentiation.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus edit_role or apply_blueprint, and no mention of prerequisites such as requiring the Manage Roles permission or a lower hierarchy position. The agent must infer usage entirely from the tool name.

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