Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_member

Edits a Discord server member’s nickname, roles, voice state, and timeout settings by specifying the server and user IDs. Use it to update moderation and voice controls in one request.

Instructions

Edit a member: nickname, roles, server mute/deafen, move/disconnect voice (channel_id), timeout (communication_disabled_until). [PATCH /guilds/{guild_id}/members/{user_id}]

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>",
      "user_id": "<user_id>"
    },
    "name": "modify_guild_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
deafNoServer-deafen in voice
muteNoServer-mute in voice
nickNo
flagsNoFlags bitfield
rolesNoRole IDs (replaces the full list)
reasonNoReason (shown in the audit log)
user_idYesUser ID
guild_idYesServer (guild) ID
channel_idNoChannel ID
communication_disabled_untilNo

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, so the safety profile is covered. The description adds the PATCH endpoint tag, which usefully signals partial-update semantics (only supplied fields change), but it says nothing about required permissions such as Manage Roles/Manage Nicknames, role-hierarchy constraints, or rate limits on role edits.

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?

A single front-loaded sentence lists capabilities in priority order, followed by a compact endpoint tag. No filler, no restatement of the tool name, and the field groupings make it scannable.

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 10-parameter mutation tool with no output schema and existing annotations, the definition covers the main edit surfaces and the partial-update model. The remaining gap is operational context — permission requirements and what happens to unspecified fields — which an agent would need before invoking it on another user.

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?

With 80% schema coverage the baseline is 3, and the description earns an extra point by mapping the opaque `channel_id` parameter to concrete behaviors (move vs. disconnect voice) and linking `communication_disabled_until` to the timeout concept. It does not explain `flags` or the interaction between `roles` replacement and hierarchy, but it adds real meaning over the schema text.

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 definition opens with a specific verb and resource ("Edit a member") and enumerates the editable surfaces — nickname, roles, mute/deafen, voice move/disconnect, timeout — which clearly separates it from read siblings like get_guild_member and from add_guild_member. It never names modify_current_guild_member, so the self-vs-other distinction is left implicit.

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 through the field list: the parenthetical "(channel_id)" hints that voice moves/disconnects belong here, and the field enumeration tells the agent what this tool is for. There is no explicit statement of when to prefer it over modify_current_guild_member or modify_guild_member_profile, and no prerequisites (permissions, role hierarchy) are given.

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