Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

add_channel_recipient

Adds a user to a group DM using channel and user IDs, optionally setting or resetting that user's nickname.

Instructions

Add a user (a friend) to a group DM. [PUT /channels/{channel_id}/recipients/{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": {
      "channel_id": "<channel_id>",
      "user_id": "<user_id>"
    },
    "name": "add_channel_recipient"
  }
}

Input Schema

NameRequiredDescriptionDefault
nickNoNickname (null or "" resets it)
user_idYesUser ID
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
access_tokenNoaccess token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive open-world write, so the safety profile is covered structurally. The description adds meaningful context that the added user must be a friend, but says nothing about what happens on failure (non-friend, DM full) or about the effect on the channel.

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 the HTTP route, with no filler. The bracketed endpoint is marginally redundant with the schema but useful for mapping to the API.

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?

A four-parameter mutation tool with no output schema; the description covers the core action and the friendship constraint but leaves error behavior and side effects (e.g., whether the recipient is notified) unstated.

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%, including the non-obvious nick-reset semantics, so the schema carries this dimension. The description adds no parameter-level meaning beyond the resource path shown.

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 concrete verb and resource ('Add a user ... to a group DM') and scopes it to a specific operation, which is clearly distinguishable from remove_channel_recipient. It falls short of 5 only because it does not contrast itself against any sibling by name.

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 'a friend' implies a precondition (the user must already be a friend) and the 'group DM' target implies usage context, but neither is stated as an explicit when-to-use rule, and no alternative tool is named.

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