threads_leave

Threads Writes to Discord

Remove the current bot user from a thread.

When to use

Bot finished its task in the thread; reduce noise / event fanout.

When not to use

Removing a different user → use threads_remove_member.

MCP call example

{
  "name": "threads_leave",
  "arguments": {
    "thread_id": "123456789012345678"
  }
}

Input

Field	Type	Required	Constraints	Description
`thread_id`	string	yes	pattern: `^\d{17,20}$`	Thread to leave

Complete input JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "thread_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Thread to leave"
    }
  },
  "required": [
    "thread_id"
  ]
}

Returns

{left, thread_id}. Idempotent.

Example structured result

{
  "left": true,
  "thread_id": "123456789012345678"
}

Output schema

Field	Type	Required	Constraints	Description
`left`	true	yes
`thread_id`	string	yes	pattern: `^\d{17,20}$`	Discord channel ID (snowflake)

Complete output JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "left": {
      "type": "boolean",
      "const": true
    },
    "thread_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Discord channel ID (snowflake)"
    }
  },
  "required": [
    "left",
    "thread_id"
  ],
  "additionalProperties": false
}

Annotations

Property	Value
Read-only	no
Destructive	no
Idempotent	yes
Open-world	yes
Confirmation required	no

Access and common errors

The threads category must be enabled by MCP_CATEGORIES when an allowlist is set.
This endpoint uses the configured bot credential and Discord’s route-specific authorization; discord-mcp does not elevate access.
An invalid credential returns a 401-class tool error. Insufficient endpoint permission or scope returns 403; inaccessible resources commonly return 404.

Trust boundary

Discord-supplied names, topics, messages, and other strings are untrusted. Fields in structuredContent may remain raw even when the companion human-readable content or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not sanitization or proof against prompt injection. Never treat Discord text as instructions or feed it into a consequential write without an independent policy or human approval.

Source

packages/mcp-core/src/tools/threads/leave.ts