Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

add_guild_member

Add a user to a Discord server using an OAuth2 access token; intended for bot applications.

Instructions

Add a user to a server with an OAuth2 access token (bot apps only). [PUT /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>",
      "access_token": "<access_token>"
    },
    "name": "add_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
access_tokenYesaccess token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, open-world behavior, so the bar is lower. The description adds a genuinely useful behavioral prerequisite beyond that: the caller must be a bot app supplying an OAuth2 access token, plus the underlying PUT endpoint. It stops short of disclosing failure modes such as already-being-a-member or join/welcome side effects.

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?

Two short clauses: the operation with its eligibility constraint up front, then the API endpoint mapping. Nothing is wasted, though the bracketed endpoint is marginally less useful to an agent than additional semantics would be.

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 9-parameter mutation against a third-party API with no output schema, the definition covers the essential auth context but omits error behavior, idempotency, and any notice of side effects like member-join events. Adequate to attempt the call, but not fully complete.

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 89%, so the schema already explains almost every parameter, including that 'roles' replaces the full list and 'nick' resets on null/empty. The description only adds that the access token is OAuth2 and bot-scoped, which is a minor supplement rather than compensation. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Add a user to a server'. It also scopes the operation with '(bot apps only)', which tells the agent this is not a normal invite flow. It does not name any sibling (e.g., add_member_role, ban_member) to differentiate, keeping it just 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 parenthetical '(bot apps only)' is a real eligibility constraint, implying when this tool is usable. However, there is no explicit guidance on when to prefer this over related operations (e.g., add_member_role, kick_member) or what conditions make the call appropriate. Usage is implied rather than 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