Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_user_settings

Update Discord account settings such as status, theme, locale, developer mode, guild folders, friend source flags, and DM privacy via a single settings patch.

Instructions

Change client settings: status, custom_status, theme, locale, developer_mode, guild_folders, friend_source_flags, DM privacy (default_guilds_restricted)… [PATCH /users/@me/settings]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "modify_user_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNotheme
localeNolocale
statusNoStatus
afk_timeoutNoAFK timeout in seconds (60, 300, 900, 1800, 3600)
animate_emojiNoanimate emoji
custom_statusNo
gif_auto_playNogif auto play
guild_foldersNoguild folders
render_embedsNorender embeds
developer_modeNodeveloper mode
timezone_offsetNotimezone offset
animate_stickersNoanimate stickers
render_reactionsNorender reactions
view_nsfw_guildsNoview nsfw guilds
convert_emoticonsNoconvert emoticons
disable_games_tabNodisable games tab
restricted_guildsNorestricted guilds
show_current_gameNoshow current game
enable_tts_commandNoenable tts command
inline_embed_mediaNoinline embed media
friend_source_flagsNofriend source flags
contact_sync_enabledNocontact sync enabled
friend_discovery_flagsNofriend discovery flags
explicit_content_filterNoMedia filter: 0 off, 1 members without roles, 2 everyone
inline_attachment_mediaNoinline attachment media
message_display_compactNomessage display compact
detect_platform_accountsNodetect platform accounts
default_guilds_restrictedNodefault guilds restricted
stream_notifications_enabledNostream notifications enabled
activity_restricted_guild_idsNoactivity restricted guild ids
allow_accessibility_detectionNoallow accessibility detection
slayer_sdk_receive_dms_in_gameNoslayer sdk receive dms in game
native_phone_integration_enabledNonative phone integration enabled
activity_joining_restricted_guild_idsNoactivity joining restricted guild ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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, and the description's 'Change' plus PATCH verb are consistent with that. It adds the set of mutable fields but says nothing about whether unspecified settings are preserved (partial vs full replacement), what permissions or auth are needed, or what side effects changes have.

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 with the verb first, a compact field list and an endpoint tag; no filler. The trailing ellipsis is slightly sloppy but honestly signals the incomplete enumeration.

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 34-parameter mutation with no output schema, the description covers what can be changed and the endpoint but omits how partial updates behave and what happens to omitted or cleared values (e.g. nulling custom_status). Annotations carry the safety profile, so the remaining gap is moderate rather than critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 97% and zero parameters are required, so the schema already documents all 34 fields; the description's job here is minimal. It correctly flags that the listed fields are a non-exhaustive sample ('…'), matching the large optional schema, and identifies the notable nested one (default_guilds_restricted, friend_source_flags).

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?

Specific verb ('Change') plus a concrete resource ('client settings') and an explicit list of affected fields, plus the underlying endpoint [PATCH /users/@me/settings]. It does not explicitly separate itself from siblings like modify_user_guild_settings or modify_notification_settings, but the 'client settings' framing and field list make the scope inferable.

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?

Usage is only implied: the field list (theme, locale, status, DM privacy) signals account-level client preferences rather than guild or notification settings, which is what separates it from the sibling modify_* settings tools. There is no explicit when-to-use/when-not statement or reference to an alternative tool.

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