Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

add_member_role

Assign a Discord role to a guild member via the Discord API, with an optional audit log reason. Use it to grant permissions by specifying server, user, and role IDs.

Instructions

Give a role to a member. [PUT /guilds/{guild_id}/members/{user_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>",
      "user_id": "<user_id>",
      "role_id": "<role_id>"
    },
    "name": "add_member_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
role_idYesRole ID
user_idYesUser ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 mutation/safety profile is supplied. The description adds nothing beyond that — no note that the role must exist and be assignable, no permission or hierarchy constraints, and no indication the PUT is idempotent or what happens on retry.

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?

Two short, front-loaded elements with zero padding: the action first, then the endpoint. It is efficient, though the bracketed route is more reference data than explanatory content.

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?

For a simple four-parameter mutation with full schema coverage and annotations but no output schema, the description is borderline adequate. It omits permission requirements and failure conditions that an agent would want before invoking an open-world write operation.

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 all four parameters are already documented in the schema, and the endpoint template helpfully maps guild_id, user_id and role_id to their positions. The description adds no further meaning, such as when the optional 'reason' matters, so the baseline 3 applies.

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 states a specific verb and resource ('Give a role to a member') and anchors it with the exact endpoint template, so the action is unambiguous. It does not distinguish itself from close siblings such as remove_member_role or add_guild_role_members, so it stops short of a 5.

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 when-to-use guidance, no prerequisites (e.g. needing Manage Roles permission or role hierarchy position), and no mention of the inverse tool remove_member_role. The intended usage is only weakly implied by the verb and endpoint.

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