Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_member_role

Destructive

Removes a specified role from a Discord server member, optionally recording a reason in the audit log. Use it to revoke access or permissions granted by that role.

Instructions

Take a role away from a member. [DELETE /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": "remove_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 destructiveHint=true and readOnlyHint=false, so removal semantics are covered structurally. The description adds only the REST endpoint path, saying nothing about permission requirements, hierarchy restrictions, idempotency when the role is absent, or what happens to the audit-log reason.

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 sentences with the action front-loaded and the endpoint appended as a parenthetical detail. Nothing is wasted, though there is also very little substance.

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 a destructive mutation with no output schema, the definition should state permission prerequisites and edge-case behavior (e.g., role not assigned). Neither is present, leaving the agent under-informed about failure modes.

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 (guild_id, user_id, role_id, reason) are already documented in the schema. The description adds no format hints or constraints beyond the schema, which is the baseline expectation.

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?

"Take a role away from a member" is a specific verb+resource, and the bracketed DELETE endpoint confirms it removes a single role assignment from one user in one guild. It is not explicitly contrasted with add_member_role, but the directional verb makes the distinction clear enough on its own.

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 or when-not-to-use guidance, no mention of prerequisites such as Manage Roles permission or role hierarchy position, and no reference to add_member_role as the inverse operation. The agent must infer all of this.

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