discord-server-mcp

create_thread

Start a Discord thread in a text or announcement channel, either standalone or from an existing message, with options for private threads and auto-archive timing.

Instructions

Start a thread in a text or announcement channel, from a message or on its own.

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

Input Schema

Name	Required	Description
`bot`	No	Use this bot (name or id) instead of choosing automatically
`name`	Yes
`server`	No	Server name or id. Optional when the bot is in one server or DISCORD_GUILD_ID is set.
`channel`	Yes	Channel or thread name, id, or message link
`dry_run`	No	Show the requests that would be made without changing anything
`private`	No	Private thread (text channels only)
`message_id`	No	Start the thread from this message
`auto_archive_minutes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations only declare readOnlyHint=false, so the description must carry behavior, and it does add real constraints: the channel-type restriction and the two creation modes. It says nothing about required permissions (manage-threads), whether private threads are allowed in announcement channels, what the default auto-archive window is, or what happens on failure.

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?

A single front-loaded sentence with no filler, and the scope constraint precedes the mode description. It is efficient, though for an 8-parameter mutation tool it could have spent a few more words on caveats without becoming bloated.

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 an 8-parameter mutating tool with no output schema and only a readOnlyHint=false annotation, the description covers the core action and channel constraint but omits permissions, defaults (auto_archive_minutes), and the private-thread restriction. It is adequate to select the tool but thin for invoking it safely.

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 75%, so the baseline is 3. The description's 'from a message or on its own' clarifies that message_id is optional and controls the creation mode, which is a small amount of meaning beyond the schema, but it adds nothing about private, auto_archive_minutes, or dry_run.

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?

States a specific verb and resource ('Start a thread') and adds scope that an agent can act on: text or announcement channels, and either from an existing message or standalone. It does not name or distinguish itself from near neighbors such as create_forum_post or create_channel, so it falls short of a 5.

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

Usage Guidelines3/5

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

Channel-type scoping implicitly tells the agent where threads can be started, and 'from a message or on its own' hints at the two invocation modes tied to message_id. There is no explicit when-to-use versus alternatives, no exclusion (e.g., forum channels need a different tool), and no stated prerequisites.

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