Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_thread_member

Destructive

Removes a specified user from a Discord thread using the thread channel ID and user ID to manage thread membership and access.

Instructions

Remove Thread Member. [DELETE /channels/{channel_id}/thread-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": {
      "channel_id": "<channel_id>",
      "user_id": "<user_id>"
    },
    "name": "remove_thread_member"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is covered; the description's DELETE route is consistent with and mildly reinforces that. It does not disclose anything further — whether removal is reversible, what permissions are required, or whether the target user is notified — so it adds little beyond the structured hints.

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 fragments, front-loaded with the action and followed by the route, with no filler or redundancy. Brevity here is not the problem; the missing content is, so it scores well on structure without earning a 5.

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

Completeness2/5

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

For a destructive, irreversible-looking membership mutation with no output schema and no annotations explaining consequences, the description should say what gets removed and under what conditions it fails or requires permission. Neither the human-readable intent nor any error or permission context is present.

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?

Schema description coverage is 100%, so the baseline is 3; the endpoint template raises it slightly by mapping channel_id and user_id to concrete path positions, clarifying that both are identifying rather than filter arguments. The third parameter, 'location', is left unexplained in both schema and description, keeping this below a 5.

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

Purpose3/5

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

The description restates the tool name ('Remove Thread Member') and adds the REST route DELETE /channels/{channel_id}/thread-members/{user_id}, which does confirm the verb and the two path-addressed resources. But the prose itself adds no scope or differentiation — an agent learns nothing about how this differs from siblings like leave_thread or remove_member_role beyond guessing from names.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no indication of when to prefer this over leave_thread (self-removal) or remove_member_role. The endpoint path hints that both a channel and a user must be supplied, but the agent must infer all routing logic on its own.

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