Skip to main content
Glama
cj-vana

Discord Server Setup MCP

by cj-vana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

edit_role

Modify a Discord role's name, color, permissions, hoist, mentionable, or position. Permissions are fully replaced with the new set.

Instructions

Edits a role's name, color, permissions, hoist, mentionable, or position. Note: permissions REPLACE the role's existing permission set. Position uses Discord's inverted scale (higher = more powerful); to reorder relative to other roles, reorder_roles is usually clearer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew name for the role
colorNoNew color as hex string or integer
hoistNoDisplay members with this role separately
roleIdYesID of the role to edit
guildIdNoGuild ID or name. Defaults to the currently selected guild.
positionNoNew raw Discord position (higher = more powerful).
mentionableNoAllow anyone to @mention this role
permissionsNoArray of Discord permission names in SCREAMING_SNAKE_CASE (e.g. VIEW_CHANNEL, SEND_MESSAGES, MANAGE_ROLES, KICK_MEMBERS, ADMINISTRATOR, USE_VAD, SEND_TTS_MESSAGES). Unknown names are rejected rather than silently ignored. Replaces the role's existing permissions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.0.1
    • addedInput schema / properties / color / description
      Added value: +"New color as hex string or integer"
    • addedInput schema / properties / guildId / description
      Added value: +"Guild ID or name. Defaults to the currently selected guild."
    • addedInput schema / properties / hoist / description
      Added value: +"Display members with this role separately"
    • addedInput schema / properties / mentionable / description
      Added value: +"Allow anyone to @mention this role"
    • addedInput schema / properties / name / description
      Added value: +"New name for the role"
    • addedInput schema / properties / permissions / description
      Added value: +"Array of Discord permission names in SCREAMING_SNAKE_CASE (e.g. VIEW_CHANNEL, SEND_MESSAGES, MANAGE_ROLES, KICK_MEMBERS, ADMINISTRATOR, USE_VAD, SEND_TTS_MESSAGES). Unknown names are rejected rather than silently ignored. Replaces the role's existing permissions."
    • removedInput schema / properties / permissions / items / enum
      Removed value: -[
-  "CREATE_INSTANT_INVITE",
-  "KICK_MEMBERS",
-  "BAN_MEMBERS",
-  "ADMINISTRATOR",
-  "MANAGE_CHANNELS",
-  "MANAGE_GUILD",
-  "ADD_REACTIONS",
-  "VIEW_AUDIT_LOG",
-  "PRIORITY_SPEAKER",
-  "STREAM",
-  "VIEW_CHANNEL",
-  "SEND_MESSAGES",
-  "SEND_TTS_MESSAGES",
-  "MANAGE_MESSAGES",
-  "EMBED_LINKS",
-  "ATTACH_FILES",
-  "READ_MESSAGE_HISTORY",
-  "MENTION_EVERYONE",
-  "USE_EXTERNAL_EMOJIS",
-  "VIEW_GUILD_INSIGHTS",
-  "CONNECT",
-  "SPEAK",
-  "MUTE_MEMBERS",
-  "DEAFEN_MEMBERS",
-  "MOVE_MEMBERS",
-  "USE_VAD",
-  "CHANGE_NICKNAME",
-  "MANAGE_NICKNAMES",
-  "MANAGE_ROLES",
-  "MANAGE_WEBHOOKS",
-  "MANAGE_GUILD_EXPRESSIONS",
-  "USE_APPLICATION_COMMANDS",
-  "REQUEST_TO_SPEAK",
-  "MANAGE_EVENTS",
-  "MANAGE_THREADS",
-  "CREATE_PUBLIC_THREADS",
-  "CREATE_PRIVATE_THREADS",
-  "USE_EXTERNAL_STICKERS",
-  "SEND_MESSAGES_IN_THREADS",
-  "USE_EMBEDDED_ACTIVITIES",
-  "MODERATE_MEMBERS",
-  "VIEW_CREATOR_MONETIZATION_ANALYTICS",
-  "USE_SOUNDBOARD",
-  "USE_EXTERNAL_SOUNDS",
-  "SEND_VOICE_MESSAGES"
-]
    • addedInput schema / properties / position / description
      Added value: +"New raw Discord position (higher = more powerful)."
    • changedInput schema / properties / position / minimum
      Previous value: -0New value: +1
    • addedInput schema / properties / roleId / description
      Added value: +"ID of the role to edit"
  2. First observedv2.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description bears full responsibility. It discloses that permissions replace the existing set and explains the inverted position scale, but does not mention auth requirements or potential side effects, such as the need for MANAGE_ROLES permission.

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 two concise sentences with no unnecessary words. It front-loads the purpose and then provides critical warnings, making it efficient and easy to parse.

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 mutation tool with 8 parameters and no output schema, the description covers key behaviors and warnings. However, it lacks mention of required permissions (e.g., MANAGE_ROLES) and does not specify that return values are not documented, leaving some context incomplete.

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 description coverage is 100%, so each parameter is documented in the schema. The description adds marginal value beyond the schema by noting the replacement behavior for permissions and the inverted position scale, but most parameter meanings are already clear from the schema.

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?

The description starts with 'Edits a role's name, color, permissions, hoist, mentionable, or position,' clearly specifying the verb and resource. It distinguishes from siblings like 'create_role' and 'reorder_roles' by focusing on editing existing role attributes and explicitly mentioning reorder_roles as clearer for reordering.

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

Usage Guidelines4/5

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

The description provides guidance by noting that permissions REPLACE the existing set and that position uses Discord's inverted scale with reorder_roles recommended for reordering. However, it does not mention required permissions (e.g., MANAGE_ROLES) or when to use this tool for other fields, leaving some gaps.

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

Deploy Server

Other Tools