Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_remove_role

Removes one or more Discord roles from a guild member to revoke access or update permissions when their responsibilities change; requires Manage Roles.

Instructions

Remove one or more roles from a member. Requires Manage 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": {
      "guildId": "<guildId>",
      "userId": "<userId>",
      "roleIds": "<roleIds>"
    },
    "name": "discord_remove_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)
roleIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the Manage Roles permission requirement, which is genuine value beyond the schema. It omits other relevant behavior: whether the change is reversible, how partial failures are handled when some roleIds are invalid, and whether bulk removal up to the schema's 20-item cap behaves atomically.

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?

Two tight sentences, front-loaded with the operation and followed by the permission constraint. Nothing is wasted or buried.

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?

This is a privileged mutation tool with no annotations, no output schema, and only 25% parameter description coverage; the description should say more about the reason parameter, the bulk limit, and permission failure behavior. As written, an agent can guess the call but not call it confidently.

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 coverage is only 25% – just guildId carries a description. The description never explains roleIds (array, 1-20 items), userId, or the optional reason (max 512 chars, presumably the audit-log reason), so it fails to compensate for the coverage gap.

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 ('Remove one or more roles from a member'), which clearly contrasts with the sibling discord_add_role. It does not explicitly name alternatives, but the operation itself is unambiguous.

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

Usage Guidelines3/5

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

It gives a real prerequisite ('Requires Manage Roles'), which helps an agent decide whether the call can succeed. It offers no guidance on when to prefer this over related tools (e.g. add_role, delete_role) or on edge cases such as removing a role the member lacks.

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