Skip to main content
Glama
discord-mcp

discord-mcp

members_bulk_add_role

Idempotent

Assign one existing role to 1–100 explicitly identified guild members in a single batch and return per-member success and failure lists. Use it for bounded bulk role grants, not single-member updates.

Instructions

Purpose: Add one role to 1-100 explicitly identified guild members.

When to use: - Assign the same existing role to a bounded list of known members.

When NOT to use: - Assigning a role to one member -> use members_add_role. - Discovering or filtering members -> use members_list first.

Returns: {role_id, succeeded_user_ids, failed_user_ids, succeeded_count, failed_count}. Each successful PUT includes an idempotent no-op when the member already has the role. An unknown member is reported as a per-member failure. Permission, rate-limit, upstream, and other infrastructure errors stop the batch; prior successful writes remain, and retrying the same request is safe because each PUT is idempotent.

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>",
      "user_ids": "<user_ids>"
    },
    "name": "members_bulk_add_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_idYesRole to add
guild_idYesGuild containing the members
user_idsYesUnique member IDs to grant the role to (1-100)
audit_reasonNoReason recorded in audit log (X-Audit-Log-Reason header)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.32.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (non-read-only, idempotent, non-destructive, open-world), and the description adds substantial context beyond them: partial-failure semantics (per-member failure for unknown members), stop-on-infrastructure-error behavior with prior writes retained, and safe retry via idempotent PUTs. That is exactly the operational detail an agent needs before issuing a batch mutation.

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?

Front-loaded with purpose, then when/when-not, then returns and failure semantics, using labeled sections that are easy to scan. The 'Returns' sentence partly duplicates the existing output schema, which is the only meaningful redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a batch mutation with partial-failure potential, the definition covers when to use it, what is returned, how unknown members are handled, and how infrastructure errors affect the batch and retries. Nothing an agent needs in order to call it correctly and interpret results is missing.

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 including audit_reason are already documented in the schema. The description restates the 1-100 bound on user_ids but adds no format, constraint, or behavioral meaning beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb ('Add'), resource ('one role'), and precise scope ('1-100 explicitly identified guild members'), and explicitly distinguishes itself from the sibling members_add_role. An agent can tell exactly what this does and which of the two add-role tools applies.

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

Usage Guidelines5/5

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

Provides explicit 'When to use' (same role, bounded list of known members) and 'When NOT to use' with named alternatives for both the single-member case (members_add_role) and the discovery case (members_list first). Nothing is left to inference.

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