Skip to main content
Glama
cj-vana

Discord Server Setup MCP

by cj-vana

create_role

Creates a Discord role with customizable name, color, permissions, and hierarchical placement above or below other roles.

Instructions

Creates a role. IMPORTANT: Discord positions are inverted — higher number = higher/more powerful, @everyone = 0 at the bottom, and a new role defaults to the BOTTOM. To make an important role rank high, pass placement:"top" (or "above"/"below" a reference role). Do not rely on raw position numbers unless you know Discord's inverted scheme.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the role (1-100 characters)
colorNoRole color as hex string (#FF0000) or integer (0-16777215)
hoistNoDisplay members with this role separately in the sidebar
guildIdNoGuild ID or name. Defaults to the currently selected guild.
positionNoRaw Discord position (higher = more powerful). Overrides placement. Prefer placement instead.
placementNoWhere to rank the role. "top" = highest the bot can assign (just under the bot), "bottom" = just above @everyone (Discord default), "above"/"below" = relative to referenceRoleId. Prefer this over raw position.
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.
referenceRoleIdNoRole ID to place the new role above/below (required when placement is "above" or "below").
Behavior4/5

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

No annotations are provided, so the description bears full burden. It discloses Discord's inverted position system, that unknown permission names are rejected, and how placement works. However, it does not mention what the tool returns (no output schema).

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?

The description is a single paragraph that front-loads the purpose and then provides crucial usage context. While slightly lengthy, every sentence adds value and the structure is logical.

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?

Given the tool complexity (9 parameters, no output schema), the description covers placement nuance and permission behavior but omits what the tool returns (e.g., the created role object). It also does not mention rate limits or idempotency, leaving some gaps.

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 100%, so baseline is 3. The description adds value by explaining the 'placement' vs 'position' trade-off and the behavior of 'permissions' array (rejecting unknown names). This goes beyond the schema descriptions.

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 tool name 'create_role' combined with the description 'Creates a role' clearly states the action and resource. It is distinct from siblings like delete_role, edit_role, and reorder_roles.

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

Usage Guidelines5/5

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

The description provides explicit guidance on using 'placement' over raw 'position' due to Discord's inverted scheme, and explains default behavior (new role at bottom). It tells when to use each option and warns against relying on raw numbers.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cj-vana/discord-setup-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server