Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

leave_thread

Destructive

Leave a Discord thread to stop receiving its updates and remove your membership. Provide the thread channel ID to exit the conversation without deleting it.

Instructions

Leave a thread. [DELETE /channels/{channel_id}/thread-members/@me]

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

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description's endpoint adds genuine context beyond that: the @me path segment signals the current user is the one removed, distinguishing it from a member-removal tool. It says nothing about side effects, permission requirements, or what happens to a thread with no remaining members.

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, with no filler. The endpoint notation is compact and useful rather than padding, though the resulting fragment style leaves no room for the caveats that would be worth one more sentence.

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 two-parameter destructive membership operation with full schema coverage and a clear annotation profile, the definition is minimally sufficient. It omits any note on required membership state, permission scope, or reversibility, which an agent performing a destructive action would benefit from.

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%, so both parameters are already documented, and the baseline of 3 applies. The endpoint syntax marginally clarifies that channel_id is a path parameter, but the optional "location" parameter is never addressed in the description.

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?

"Leave a thread" is a specific verb plus resource, and the bracketed endpoint confirms it removes the calling user from a thread. It does not distinguish itself from adjacent siblings such as leave_voice_channel or remove_thread_member, so the agent must infer that this is self-removal rather than removing someone else.

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 explicit when-to-use statement, no preconditions (must be a thread member), and no named alternative. The only implicit cue is the DELETE verb, which hints at exiting an existing membership but gives no guidance on when to pick this over remove_thread_member or leave_guild.

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