Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Bulk update roles

bulk_update_roles
Destructive

Assign or remove one role across every member matching a filter, such as bots, join dates, or existing roles. The first call previews the affected count and returns a token to confirm.

Instructions

Add or remove a role across every member matching a filter. Safe to call directly: the first call returns the affected count and a confirm_token; repeating the call with the token applies the change. Walks up to 3000 members and reports if it hits the cap.

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": {
      "action": "<action>",
      "role": "<role>"
    },
    "name": "bulk_update_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesRole name or ID.
guildNoGuild (server) name or ID. Omit to use the default guild.
actionYes
filterNo
dry_runNo
confirm_tokenNoThe token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token / description
      Added value: +"The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree."
  2. Changed2 schema fields changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / filter / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description still adds real context beyond them: a two-phase preview/confirm protocol, the fact that the first call mutates nothing, the 3000-member walk limit, and that cap overflow is reported. Those are exactly the traits an agent needs before invoking a destructive bulk operation.

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?

Three tight sentences with the action front-loaded and the safety protocol immediately after; every clause carries information an agent needs. No filler, no restatement of the tool name.

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 destructive, nested-filter, six-parameter tool with no output schema, the description covers the critical behavioral contract: confirmation flow, return of an affected count, and the traversal cap. The remaining hole is dry_run and any permission/partial-failure behavior, which leaves it just short of complete.

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 coverage is only 50%, and the description compensates for the most dangerous gap by explaining the confirm_token's role in the preview/apply sequence. However, dry_run carries no description in either the schema or the description, leaving its interaction with the token flow ambiguous, and no filter semantics are added beyond 'matching a filter'.

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 opens with a specific verb pair and resource: 'Add or remove a role across every member matching a filter.' The 'every member matching a filter' scope implicitly separates it from per-member siblings like assign_role, but it never names an alternative explicitly, so differentiation stops short of the top band.

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?

It gives concrete operational guidance: call directly, read the affected count and confirm_token, then repeat with the token to apply. That is the essential when/how instruction. It stops short of stating when to prefer a single-member tool or what to do when the cap is hit.

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