Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_thread_from_message

Start a thread from an existing message to organize replies and keep channel discussions focused; provide channel ID, message ID, and thread name.

Instructions

Start a thread from an existing message. [POST /channels/{channel_id}/messages/{message_id}/threads]

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

Input Schema

NameRequiredDescriptionDefault
nameYesName
locationNolocation
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
message_idYesMessage ID
rate_limit_per_userNoSlowmode in seconds (0-21600)
auto_archive_durationNoAuto-archive after inactivity, in minutes: 60, 1440, 4320 or 10080

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive operation. The description adds the REST endpoint and HTTP method, confirming a POST mutation, but does not disclose side effects, permission requirements, or what happens to the source message 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with the core action front-loaded, and the endpoint provides useful implementation context. The bracketed REST path is somewhat redundant with the tool name but does not undermine clarity.

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?

With six parameters fully covered by the schema and annotations declaring the safety profile, the definition is adequate but thin. It omits differentiation from the 'create_thread' sibling and does not explain return behavior or permissions, which would help for a thread-creation mutation.

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 all six parameters are already documented in the input schema, including channel_id, message_id, name, slowmode, and auto-archive duration. The description adds no parameter meaning beyond what the schema provides, which is the baseline expectation when coverage is complete.

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 states a specific verb and resource ('Start a thread') and clarifies the source ('from an existing message'), so the operation is unambiguous. However, it does not distinguish this from the sibling 'create_thread' tool, leaving the agent to infer the difference.

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?

Usage is only implied: 'from an existing message' suggests when this tool applies, but there is no explicit guidance on when to choose it over 'create_thread' or any stated prerequisites. The agent must infer the selection criteria.

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