Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_create_thread

Create a Discord thread by branching from an existing message or starting a standalone thread in a text channel. Set auto-archive duration and get the new thread ID.

Instructions

Create a thread, either branching from an existing message (pass message_id) or as a standalone thread in a text channel (omit message_id). Standalone creation requires a parent text channel and fails if channel_id is itself a thread. Requires the Create Public Threads permission. Returns the new thread's ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the thread to create (max 100 characters).
channel_idYesID (snowflake) of the parent text channel. For a message-based thread, the channel containing message_id.
message_idNoOptional. Message to branch the thread from. If omitted, a standalone thread is created in the channel.
auto_archive_durationNoMinutes of inactivity before auto-archiving: 60, 1440, 4320, or 10080. Default 1440 (24h).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / auto_archive_duration / default
      Added value: +1440
    • addedInput schema / properties / auto_archive_duration / enum
      Added value: +[
+  60,
+  1440,
+  4320,
+  10080
+]
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / message_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed4 schema fields changedv1.6.0
    • changedInput schema / properties / auto_archive_duration / description
      Previous value: -"Auto-archive after N minutes of inactivity (60, 1440, 4320, 10080). Default 1440 (24h)."New value: +"Minutes of inactivity before auto-archiving: 60, 1440, 4320, or 10080. Default 1440 (24h)."
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the parent text channel. For a message-based thread, the channel containing message_id."
    • changedInput schema / properties / message_id / description
      Previous value: -"Optional: message to start the thread from. If omitted, creates a standalone thread."New value: +"Optional. Message to branch the thread from. If omitted, a standalone thread is created in the channel."
    • changedInput schema / properties / name / description
      Previous value: -"Thread name."New value: +"Name of the thread to create (max 100 characters)."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With annotations present (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description still adds substantial context: the required 'Create Public Threads' permission, the failure condition when channel_id is a thread, and the return value ('Returns the new thread's ID'). These are exactly the kind of behavioral disclosures that go beyond structured annotations.

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?

Three sentences with zero filler: the first states purpose and mode selection, the second covers the constraint, and the third covers permission and return value. Every sentence earns its place, and the most important information is front-loaded.

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

Completeness5/5

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

For a 4-parameter create tool with full schema coverage and a safety-relevant annotation set, the description covers everything an agent needs: the two invocation modes, the failure condition, the auth requirement, and the return value. With no output schema, disclosing the returned thread ID was an important gap that the description fills.

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 description coverage is 100%, so the schema already fully documents all four parameters, including the enum values for auto_archive_duration and the optional semantics of message_id. The description adds only marginal value by clarifying the interplay between channel_id and message_id and the standalone-channel constraint, which warrants the baseline score of 3.

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 opens with a specific verb+resource ('Create a thread') and immediately distinguishes the two modes of operation: branching from an existing message via message_id versus standalone creation in a text channel. This clearly differentiates it from sibling tools like discord_create_channel and discord_create_forum_post without needing to name them.

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

Usage Guidelines4/5

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

The description gives clear operational context: when to pass message_id versus omit it, and it states an explicit constraint ('fails if channel_id is itself a thread'), which effectively warns against misuse. However, it does not point to any alternative tool (e.g., discord_create_forum_post for forum channels), so the exclusion guidance is incomplete.

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