Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

join_thread

Join a Discord thread by channel ID to add the authenticated account to the thread and enable participation in its conversation.

Instructions

Join a thread. [PUT /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": "join_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

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds only the HTTP endpoint (PUT /channels/{channel_id}/thread-members/@me), which hints at an idempotent self-membership write but is not explained in plain terms. It says nothing about what membership change occurs, whether it is idempotent, or what errors arise if already a member or the thread is archived.

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?

The description is a single short sentence plus the endpoint reference, with no filler or restated title. It is efficient, though its brevity comes at the cost of guidance rather than because it is well-optimized.

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 mutation tool that sits among several similar join/add-member tools, the definition leaves out the distinctions and behavioral details an agent needs to select and call it confidently. There is no output schema, so the description should carry more of that burden than it does.

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 parameters are documented in the schema. The description adds no meaning beyond that, but with full schema coverage a baseline of 3 is appropriate.

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 states a verb and resource ('Join a thread'), which is understandable but does not distinguish it from sibling tools like add_thread_member, join_voice_channel, or join_guild. An agent must infer that this joins the calling user to a thread specifically.

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 or when-not-to-use guidance. The description does not explain how this differs from add_thread_member (adding another user) or leave_thread, both of which are plausible alternatives the agent must disambiguate 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