Skip to main content
Glama

discord_create_thread

Create organized discussion threads in Discord channels to structure conversations around specific topics or messages.

Instructions

Create a thread from an existing message or as a standalone thread in a channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
nameYesThread name.
message_idNoOptional: message to start the thread from. If omitted, creates a standalone thread.
auto_archive_durationNoAuto-archive after N minutes of inactivity (60, 1440, 4320, 10080). Default 1440 (24h).

Implementation Reference

  • The handler implementation for 'discord_create_thread' which creates a thread from a message or as a standalone thread.
    case "discord_create_thread": {
      const channel = await getTextChannel(args.channel_id as string);
      const duration = (args.auto_archive_duration as number) ?? 1440;
      if (args.message_id) {
        const msg = await channel.messages.fetch(args.message_id as string);
        const thread = await msg.startThread({
          name: args.name as string,
          autoArchiveDuration: duration as 60 | 1440 | 4320 | 10080,
        });
        return { content: [{ type: "text", text: `✅ Thread "${thread.name}" created from message (id: ${thread.id}).` }] };
      } else {
        const thread = await channel.threads.create({
          name: args.name as string,
          autoArchiveDuration: duration as 60 | 1440 | 4320 | 10080,
          type: ChannelType.PublicThread,
        });
        return { content: [{ type: "text", text: `✅ Thread "${thread.name}" created (id: ${thread.id}).` }] };
      }
    }
  • The tool definition and input schema for 'discord_create_thread'.
    {
      name: "discord_create_thread",
      description: "Create a thread from an existing message or as a standalone thread in a channel.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          name: { type: "string", description: "Thread name." },
          message_id: { type: "string", description: "Optional: message to start the thread from. If omitted, creates a standalone thread." },
          auto_archive_duration: { type: "number", description: "Auto-archive after N minutes of inactivity (60, 1440, 4320, 10080). Default 1440 (24h)." },
        },
        required: ["channel_id", "name"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('Create') which implies a write/mutation operation, but doesn't disclose behavioral traits like required permissions, rate limits, error conditions, or what happens on success (e.g., thread ID returned). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the core action and immediately clarifies the two creation methods. There is zero waste—every word contributes to understanding the tool's purpose and basic usage.

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?

Given no annotations and no output schema, the description is incomplete for a mutation tool. It covers the basic purpose and parameter implications but lacks critical context like permissions, return values, error handling, or rate limits. The schema provides some parameter details, but overall completeness is minimal viable.

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

Parameters4/5

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

Schema description coverage is 75% (3 of 4 parameters have descriptions). The description adds value by clarifying that 'message_id' is optional and its omission creates a standalone thread, which isn't in the schema. It also implies 'channel_id' and 'name' are required, matching the schema. The description compensates well for the partial schema coverage.

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 action ('Create a thread') and specifies two methods: 'from an existing message' or 'as a standalone thread in a channel'. It distinguishes from siblings like 'discord_create_channel' or 'discord_create_forum_post' by focusing on threads, but doesn't explicitly differentiate from 'discord_create_forum_channel' which also creates threaded content. The purpose is clear but could be more specific about thread types.

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?

The description implies usage context by mentioning two creation methods (from message or standalone), but doesn't provide explicit guidance on when to choose one over the other or mention alternatives. No prerequisites, permissions, or exclusions are stated. It offers basic context but lacks detailed when/when-not instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server