discord-mcp

discord_remove_role

Idempotent

Remove a role from a Discord member to update permissions or revert an assignment. Requires Manage Roles permission and role below bot's highest role; idempotent so missing roles are ignored.

Instructions

Remove a role from a member. Requires the Manage Roles permission, and the role must be below the bot's highest role. Idempotent: removing a role the member doesn't have has no effect. Reverses discord_add_role.

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": "discord_remove_role"
  }
}

Input Schema

Name	Required	Description
`reason`	No	Optional reason recorded in the server audit log.
`role_id`	Yes	ID (snowflake) of the role to remove.
`user_id`	Yes	Discord user ID (snowflake) of the member to remove the role from.
`guild_id`	Yes	Discord server (guild) ID (snowflake).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.0Sep 6, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed3 schema fields changedv2.0.0Jun 27, 2026
- addedInput schema / properties / guild_id / pattern
```
Added value: +"^\\d{17,20}$"
```
- addedInput schema / properties / role_id / pattern
```
Added value: +"^\\d{17,20}$"
```
- addedInput schema / properties / user_id / pattern
```
Added value: +"^\\d{17,20}$"
```

Changed4 schema fields changedv1.6.0May 28, 2026

addedInput schema / properties / guild_id / description

Added value: +"Discord server (guild) ID (snowflake)."

addedInput schema / properties / reason / description

Added value: +"Optional reason recorded in the server audit log."

addedInput schema / properties / role_id / description

Added value: +"ID (snowflake) of the role to remove."

addedInput schema / properties / user_id / description

Added value: +"Discord user ID (snowflake) of the member to remove the role from."

Addedv1.5.0May 8, 2026
Removedv1.0.0May 1, 2026
First observedv0.1.0Mar 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description goes well beyond the annotations by explaining the exact idempotency behavior ('removing a role the member doesn't have has no effect') and the permission/hierarchy requirements. It also clarifies the relationship to discord_add_role, which is behavioral context not present in the structured data. No contradiction with annotations; idempotentHint and destructiveHint are both consistent.

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?

Four short sentences, each contributing distinct value: the action, the prerequisites, the idempotency detail, and the sibling relationship. It is front-loaded with the main verb and resource, and there is zero filler or repetition of schema content.

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 no output schema, the description covers the essential context: what it does, permissions, role hierarchy, idempotent behavior, and relation to a sibling. It doesn't mention possible error cases (e.g., member not in guild, role not found), but these are reasonably inferred from standard Discord behavior and the schema's snowflake patterns. Overall, the agent has enough to use it correctly in most scenarios.

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%, with each parameter (guild_id, user_id, role_id, reason) already documented. The description adds no additional parameter-level meaning, so the baseline of 3 applies. The requirement about the bot's role hierarchy provides some context for role_id but is not a direct parameter semantic.

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 opens with a specific verb and resource ('Remove a role from a member') that unambiguously states the action. It distinguishes itself from siblings by explicitly noting it 'Reverses discord_add_role,' differentiating it from role-editing or role-deletion tools. The name itself is also descriptive.

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 clear context for when to use the tool: it reverses discord_add_role, implying the primary use case is undoing a role assignment. It also states prerequisites (Manage Roles permission, role must be below the bot's highest role), which helps the agent decide if the tool can be invoked. It doesn't explicitly list alternatives for when not to use it, but the named sibling relationship gives solid guidance.

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

Deploy Server