Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

bulk_modify_user_guild_settings

Change notification settings for several Discord servers in one request, so you can manage alerts across guilds without editing each server separately.

Instructions

Change notification settings for several servers at once. [PATCH /users/@me/guilds/settings]

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": {
      "guilds": "<guilds>"
    },
    "name": "bulk_modify_user_guild_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildsYesguilds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare non-read-only, non-destructive and open-world behavior; the description only adds the PATCH endpoint. It says nothing about atomicity, partial failure across guilds, required auth scopes, or what a response contains for a multi-target 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?

One front-loaded sentence plus an endpoint tag; nothing is wasted. The endpoint tag is mildly useful for API-literate agents but borders on filler.

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

Completeness3/5

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

For a single-parameter mutation with a nested, untyped object and no output schema, the definition covers the what but not the shape of the payload or failure behavior. Adequate to select the tool, thin for invoking it correctly.

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 the baseline is 3, but the single 'guilds' parameter is a free-form object with additionalProperties and no documented shape. The description does not explain the map structure (guild id to settings), which the schema leaves entirely open.

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 concrete verb and resource ('Change notification settings') with an explicit scope qualifier ('for several servers at once'), which lets an agent distinguish it from the single-guild sibling modify_user_guild_settings. It does not name that sibling explicitly, so it falls short of a 5.

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 'for several servers at once' implies the bulk case is the reason to pick this tool, but there is no explicit when-to-use guidance, no mention of when to prefer the single-guild alternative, and no prerequisites or caveats.

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