Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_role

Edit a Discord server role’s name, colors, permissions, icon, hoist, and mentionable settings so you can update access and appearance without recreating the role.

Instructions

Edit a role: name, colour, permissions, hoist, mentionable, icon. [PATCH /guilds/{guild_id}/roles/{role_id}]

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": {
      "guild_id": "<guild_id>",
      "role_id": "<role_id>"
    },
    "name": "modify_guild_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNo
nameNo
hoistNo
colorsNo
reasonNoReason (shown in the audit log)
role_idYesRole ID
guild_idYesServer (guild) ID
descriptionNo
mentionableNo
permissionsNo
unicode_emojiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-destructive, open-world mutation, so the description does not contradict them. The description adds the endpoint and the set of editable fields, but it omits permission requirements, audit-log reason behavior, and whether the update is partial or complete.

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 definition is a single front-loaded sentence plus the HTTP endpoint in brackets. It is appropriately sized for an edit tool and contains no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 and low schema description coverage, the description is too thin. It does not explain required IDs, optional-null behavior, permissions syntax, audit-log reason, or what happens to unspecified role attributes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 27%, so the description needs to compensate, but it names only some fields (name, colour, permissions, hoist, mentionable, icon). It omits required guild_id and role_id semantics, the reason audit-log parameter, description, unicode_emoji, and the gradient colors object, and it does not clarify the permissions format beyond the schema.

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: "Edit a role", then lists editable attributes and the PATCH endpoint. This clearly distinguishes it from create/delete/get role operations, though it does not explicitly separate it from the nearby modify_guild_role_positions sibling.

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 explicit when-to-use guidance, no prerequisites, and no named alternative such as modify_guild_role_positions for reordering roles. The agent must infer usage purely from the tool name and the field list.

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