Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

add_guild_role_members

Assign a Discord role to multiple server members at once, up to 30 per request, with an optional audit-log reason.

Instructions

Give a role to several members at once (max 30). [PATCH /guilds/{guild_id}/roles/{role_id}/members]

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>",
      "role_id": "<role_id>",
      "member_ids": "<member_ids>"
    },
    "name": "add_guild_role_members"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/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 write and safety profile is covered. The description contributes the 30-member batch limit, which is real added context, but says nothing about permission requirements, whether the audit-log reason applies, or what happens if some member_ids are invalid or already have the role.

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 fragments with zero filler; the operation comes first and the limit is attached inline. The bracketed HTTP endpoint is mildly technical but does convey the PATCH target for advanced use.

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 straightforward 4-parameter mutation with full schema coverage, no output schema and annotations covering safety, the description supplies the essential batch-size constraint. Remaining gaps (permission prerequisites, partial-failure behavior) are secondary for a tool this simple, though they would have earned a 5.

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 description coverage is 100%, so all four parameters are documented in the schema and the baseline is 3. The description adds modest value by framing member_ids as a plural batch and tying the max-30 constraint to that parameter, giving the agent a concrete bound the schema lacks.

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?

States a concrete verb and resource ('Give a role to several members at once') plus a hard cap of 30, which implicitly contrasts with the singular add_member_role sibling. It doesn't name the alternative explicitly, so the agent must infer the bulk-vs-single distinction from the phrase 'several ... at once'.

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?

The phrase 'at once (max 30)' implies this is the bulk path and gives a batch ceiling, which is useful selection guidance. There is no explicit when-to-use/when-not statement, no mention of preferring add_member_role for single assignments, and no prerequisites such as the bot needing Manage Roles.

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