Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_role

Create a Discord server role with custom name, color, icon, and permissions like MANAGE_MESSAGES. Set hoist and mentionable options to control how members see and use the role.

Instructions

Create a role. permissions accept names like ["MANAGE_MESSAGES"]. [POST /guilds/{guild_id}/roles]

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>"
    },
    "name": "create_guild_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNo
nameNo
hoistNo
colorsNoRole colours {primary_color, secondary_color, tertiary_color} (gradient roles)
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
descriptionNo
mentionableNo
permissionsNoPermissions: bitfield string, or names like ["VIEW_CHANNEL","SEND_MESSAGES"]
unicode_emojiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the raw HTTP endpoint, with no mention of permission requirements, audit-log behavior, rate limits, or what a created role defaults to. For a creation mutation with ten parameters, that is thin.

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

Conciseness4/5

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

Three short fragments, front-loaded with the purpose and ending with the endpoint, with zero filler. It is arguably too terse, but nothing is wasted.

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?

With ten parameters, a nested colors object, no output schema and only 40% schema coverage, the description does not supply enough to invoke this correctly. An agent gets no sense of required versus optional fields, default role state, or what the response contains.

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 40%, and the one parameter the description touches (permissions, with a ["MANAGE_MESSAGES"] example) is already documented in the schema itself. The nested colors object, icon/unicode_emoji interplay, hoist, mentionable and reason receive no additional explanation in the description, leaving the coverage gap unaddressed.

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?

"Create a role" states a specific verb and resource, and the bracketed endpoint confirms the object being created (a guild role). It does not distinguish this from siblings like modify_guild_role or delete_guild_role, but the create-vs-modify split is inferable from the verb alone.

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 use this versus modify_guild_role, nor any prerequisites (e.g. needing Manage Roles permission) or notes about what a newly created role can be used for. The agent must infer everything from the name and the sibling 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