Skip to main content
Glama

discord_create_forum_post

Create a new forum post (thread) in a Discord channel by specifying the channel ID, title, content, and optional tags.

Instructions

Create a new post (thread) in a forum channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forum_channel_idYes
titleYesThe post title (thread name).
contentYesThe initial message content of the post.
applied_tagsNoArray of tag IDs to apply to the post.

Implementation Reference

  • The handler logic for creating a forum post (a new thread) in a Discord forum channel.
    case "discord_create_forum_post": {
      const forum = await getForumChannel(args.forum_channel_id as string);
      const thread = await forum.threads.create({
        name: args.title as string,
        message: { content: args.content as string },
        appliedTags: (args.applied_tags as string[] | undefined) ?? [],
      });
      return { content: [{ type: "text", text: `✅ Forum post "${thread.name}" created (id: ${thread.id}) in #${forum.name}.` }] };
    }
  • The MCP tool definition and input schema for discord_create_forum_post.
      name: "discord_create_forum_post",
      description: "Create a new post (thread) in a forum channel.",
      inputSchema: {
        type: "object",
        properties: {
          forum_channel_id: { type: "string" },
          title: { type: "string", description: "The post title (thread name)." },
          content: { type: "string", description: "The initial message content of the post." },
          applied_tags: {
            type: "array",
            items: { type: "string" },
            description: "Array of tag IDs to apply to the post.",
          },
        },
        required: ["forum_channel_id", "title", "content"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool creates a post, implying a write operation, but fails to mention permissions required, rate limits, whether the action is reversible, or what happens on success/failure. This leaves critical behavioral traits unspecified for a mutation tool.

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, clear sentence with no wasted words. It is front-loaded with the core action and resource, making it efficient and easy to parse, which is ideal for conciseness.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error handling, return values, and usage context. Given the complexity of creating a forum post in Discord, more information is needed to guide the agent effectively.

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 75%, with three parameters having descriptions and one ('forum_channel_id') lacking. The description does not add any parameter semantics beyond what the schema provides, such as explaining what a 'forum_channel_id' is or format examples. With high schema coverage, the baseline score of 3 is appropriate, but no extra value is added.

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') and resource ('new post (thread) in a forum channel'), making the purpose immediately understandable. However, it does not explicitly differentiate from similar tools like 'discord_create_thread' or 'discord_reply_to_forum', which could cause confusion about when to use this specific tool versus its siblings.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'discord_create_thread' and 'discord_reply_to_forum', the agent lacks explicit instructions on context, prerequisites, or exclusions, leaving usage ambiguous.

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