discord-server-mcp

edit_role

Modify a Discord role's name, color, icon, mentionability, or permissions, including replacing all permissions or adding/removing specific ones. Use dry-run to preview changes.

Instructions

Edit a role. "permissions" replaces all of them; use add_permissions/remove_permissions to change a few. 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": {
      "role": "<role>"
    },
    "name": "edit_role"
  }
}

Input Schema

Name	Required	Description
`bot`	No	Use this bot (name or id) instead of choosing automatically
`name`	No
`role`	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, or "none"
`icon_image`	No	Image path or URL, or "none"
`mentionable`	No
`permissions`	No
`add_permissions`	No
`shown_separately`	No
`remove_permissions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the burden and does so credibly by disclosing the destructive semantic that "permissions" replaces the entire permission set. That is the key behavior an agent could otherwise get wrong. It omits prerequisites (ManageRoles) and confirmation/rate-limit behavior, keeping it below a 5.

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 critical rule about replacement semantics is front-loaded, which is good structure. But the inline list of 51 permission names consumes the bulk of the text and makes the definition heavy to parse, even though the schema provides no enum to substitute for it.

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 14-parameter mutation with no output schema and minimal annotations, the description covers the highest-risk unknowns: what gets destroyed and which values are legal. It leaves gaps around the non-permission fields and permission requirements, but the core hazards an agent must know before calling are addressed.

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 43% and no parameter has an enum, so the description's main contribution is explaining replace-vs-add/remove semantics for permissions and listing all valid permission names, which prevents invalid values. It adds nothing for name, color, mentionable, or shown_separately, so roughly half the undocumented parameters remain unclarified.

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 opens with a specific verb+resource, "Edit a role," which is immediately distinguishable from create_role and delete_role in the sibling list. It does not explicitly name those siblings, but the operation is unambiguous.

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 clearly routes the agent between parameter strategies ("permissions" replaces all of them; use add_permissions/remove_permissions to change a few), which is genuinely useful selection guidance. However, it gives no guidance about when to use edit_role versus create_role/delete_role, when to prefer a dry_run preview, or what permissions the actor needs.

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