Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_channel_recipient

Destructive

Remove a user from a group direct message you own by providing the channel ID and user ID. Use it to manage group DM membership and revoke recipient access.

Instructions

Remove a user from a group DM you own. [DELETE /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": "remove_channel_recipient"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known; the description adds genuinely new information in the form of the ownership/authorization prerequisite required to perform the removal. It does not describe side effects on the removed user or the remaining group, which keeps it below a 5.

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?

Two compact sentences with the core action and the ownership constraint front-loaded, followed by a bracketed endpoint reference. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with full schema coverage and annotations that already flag destructiveness, the description supplies the remaining critical fact (ownership requirement) and the underlying route. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so both channel_id and user_id are already documented; the description contributes only the endpoint template showing they are path parameters. That is a marginal addition over the schema, matching the baseline for fully covered parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Remove') plus the exact resource and scope ('a user from a group DM you own'), which cleanly separates it from siblings like add_channel_recipient or remove_thread_member. The appended REST endpoint reinforces the precise operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'you own' establishes a clear precondition for when this tool is applicable, and 'group DM' narrows the channel type. It stops short of naming an alternative tool or an explicit when-not-to-use case, so it is strong context rather than full routing guidance.

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