mcp-discord-bridge

create_thread

Create a new thread in a Discord text channel by specifying the channel and thread name, with an option to start from a specific message.

Instructions

Create a new thread in a text channel

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

Input Schema

Name	Required	Description
`channel_id`	Yes
`name`	Yes	Thread name
`message_id`	No	Message ID to start thread from (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 25, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose side effects (e.g., whether creation requires specific permissions, rate limits, or what happens if the thread already exists). The behavioral insight is minimal.

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?

The description is a single, clear sentence with no extraneous information. It is appropriately concise and front-loaded.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, permissions, or when to use this tool over alternatives like create_forum_post. The agent lacks context for correct invocation.

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?

The input schema covers 67% of parameters with descriptions. The description adds no extra meaning beyond the schema; it does not clarify the format or constraints of channel_id, name length, or how message_id modifies behavior. Baseline score of 3 is appropriate as the schema already provides some information.

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?

The description explicitly states the action ('Create'), the resource ('a new thread'), and the location ('in a text channel'). This clearly distinguishes it from siblings like archive_thread, delete_thread, and join_thread.

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?

The description provides no guidance on when to use this tool versus other thread-related tools (e.g., join_thread, archive_thread) or any prerequisites. The agent receives no context about channel permissions or thread limits.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.