Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create thread

create_thread

Start threads in text or announcement channels as standalone, message-branched, or invite-only private discussions; for forum posts, use a separate forum-post tool.

Instructions

Start a thread in a text or announcement channel: standalone, branched from a message when message_id is given, or private (invite-only) when asked. For a post in a forum channel, use create_forum_post instead.

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

NameRequiredDescriptionDefault
nameYes
guildNoGuild (server) name or ID. Omit to use the default guild.
channelYesParent channel name or ID.
privateNoInvite-only thread; only works standalone.
message_idNoBranch the thread from this message (its ID or link).
slowmode_secondsNo
auto_archive_minutesNoInactivity timeout: 60, 1440, 4320, or 10080. Default 1440.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / message_id / description
      Previous value: -"Branch the thread from this message."New value: +"Branch the thread from this message (its ID or link)."
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare this is a non-read-only, non-destructive write operation; the description adds useful behavioral context about thread modes, branching from a message, and invite-only privacy. It does not mention required channel permissions, notification side effects, or what is returned, so it stops short of full transparency.

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 dense sentence that front-loads the core purpose and modes, followed by the forum-channel alternative. It is efficient with no wasted framing, though the clause structure is somewhat compressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter creation tool with an output schema absent, it covers the essential purpose and key mode distinctions. It omits permission requirements, return-value expectations, and slowmode/archive behavior, which are secondary but still useful context.

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 71%, so the description partially compensates by explaining message_id as branching and private as invite-only. It does not explain name, guild, channel, slowmode_seconds, or auto_archive_minutes semantics beyond what the schema provides, leaving some parameters to the schema alone.

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?

States a specific verb and resource (start a thread) and distinguishes three creation modes: standalone, branched via message_id, and private invite-only. It also explicitly names the sibling tool to use for forum posts, so the agent can differentiate it from create_forum_post.

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

Usage Guidelines5/5

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

Gives clear when-to-use guidance by mapping modes to parameters, and explicitly routes forum-channel posts to create_forum_post instead. The alternative is named with the exact condition that selects it.

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