Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_user_guild_settings

Update Discord server or DM notification settings to mute alerts, suppress @everyone/roles, set message notification levels, and apply channel overrides.

Instructions

Notification settings for a server (use guild_id "@me" for DMs): mute, suppress @everyone/roles, message_notifications, channel_overrides. [PATCH /users/@me/guilds/{guild_id}/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": {
      "guild_id": "<guild_id>"
    },
    "name": "modify_user_guild_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNoFlags bitfield
mutedNomuted
guild_idYesServer (guild) ID
mobile_pushNomobile push
mute_configNo
suppress_rolesNosuppress roles
channel_overridesNoMap of channel_id -> {muted, mute_config, message_notifications, collapsed}
notify_highlightsNo0 default, 1 disabled, 2 enabled
suppress_everyoneNosuppress everyone
hide_muted_channelsNohide muted channels
message_notificationsNo0 all, 1 mentions only, 2 nothing, 3 inherit
mute_scheduled_eventsNomute scheduled events

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 safety profile is covered. The description adds the HTTP endpoint and the @me sentinel, but does not explain partial-update semantics (are unspecified fields left untouched or reset?), auth requirements, or what the response contains — the main behavioral question an agent would have for a 12-field settings 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?

A single dense sentence plus the endpoint reference; the most important detail (guild_id "@me" for DMs) is front-loaded and nothing is redundant. The bracketed endpoint notation is slightly cryptic but costs almost no space and confirms the write semantics.

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?

With 12 parameters, nested objects (mute_config, channel_overrides) and no output schema, the definition covers the surface area reasonably because the schema carries 92% coverage. Gaps remain around merge/patch semantics for nested overrides, the meaning of flags/notify_highlights beyond schema snippets, and return behavior, leaving it only minimally adequate for a mutation of this complexity.

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 92%, so the schema already documents nearly every field; the baseline would be 3. The description nonetheless contributes meaning the schema lacks: guild_id accepts the literal "@me" for DMs, and it groups the fields into a coherent settings concept (mute/suppress/message_notifications/channel_overrides), which helps an agent map a user request onto the right parameters.

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 names the resource precisely (per-server notification settings) and enumerates the main knobs it controls (mute, suppress @everyone/roles, message_notifications, channel_overrides), with the PATCH endpoint confirming it is a mutation. It is distinguishable from global siblings like modify_user_settings/modify_notification_settings, though the verb 'modify/update' is never stated outright and must be inferred from the bracketed HTTP method.

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 one concrete usage hint — pass guild_id "@me" for DM settings — which is genuinely useful for choosing the right target. It offers no guidance on when to use this versus bulk_modify_user_guild_settings or the global notification-setting siblings, and no prerequisites or exclusions are stated.

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