Discord MCP

Overview Schema Source Related Servers Discussions Admin

create_thread

Start a Discord thread in a channel by providing channel ID and thread data including name and type. Specify auto_archive_duration to control automatic archiving.

Instructions

Start a thread; data includes name, type and optional auto_archive_duration.

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

Input Schema

Name	Required	Description	Default
`data`	Yes
`channel_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

C2.8/5.0

Behavior3/5

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

The annotations already indicate that the tool is not read-only and not destructive, and the description confirms a mutating action. However, it does not describe potential side effects, errors, or constraints beyond starting a thread.

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, concise sentence that directly conveys the core operation. It has no unnecessary filler or repetition.

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?

The tool has no output schema, and the description does not indicate what the tool returns or how to interpret the result. This leaves the agent with incomplete context for confirming success or handling the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides no field-level documentation, and the description only vaguely mentions that data includes name, type, and optional auto_archive_duration. It does not explain the channel_id parameter or clarify the structure of the nested data object, which is fully open-ended.

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?

The description clearly states the primary action ('Start a thread') and names the resource (thread). It is distinct enough from general 'create' or 'send' actions, though it does not explicitly differentiate from sibling tools like create_channel.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives such as create_channel or send_message. There is no mention of prerequisites, ideal use cases, or situations where another tool would be more appropriate.

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