discord-mcp

Create forum post

discord_create_post

Creates a new forum post in a Discord forum channel with a title, body, and optional tags, helping users publish structured discussions that follow forum guidelines.

Instructions

Create a new post in a forum channel with a title, body and tags (tag names, see discord_list_forum_tags). Follow the forum's own post guidelines (shown as the forum topic in discord_list_channels).

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": {
      "forum_id": "<forum_id>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "discord_create_post"
  }
}

Input Schema

Name	Required	Description
`tags`	No
`embed`	No	A formatted card (title, description, colour bar, fields)
`title`	Yes
`content`	Yes	First message of the post
`forum_id`	Yes	Forum channel ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds prerequisite behavior (tag names must be resolved first, forum guidelines must be obeyed) but says nothing about failure modes such as an invalid tag name, or that the post is immediately visible in the forum.

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?

Two sentences, front-loaded with the action and required inputs, then the two prerequisite lookups. No filler and nothing repeated from the schema or annotations.

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 five-parameter create tool with a nested embed and no output schema, the description covers the main call flow and the prerequisite lookups an agent would otherwise get wrong. The unaddressed embed parameter and lack of any post-creation outcome detail are the remaining gaps.

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 coverage is only 60%, and the description adds a genuinely error-preventing semantic: tags are tag NAMES, not IDs, with a pointer to discord_list_forum_tags. It covers title, content and tags but says nothing about the nested embed parameter, whose meaning has to come entirely from the schema.

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?

States a specific verb and resource ('Create a new post in a forum channel') and enumerates the three core inputs (title, body, tags). It is clearly distinct from admin/thread siblings, though it never explicitly contrasts with discord_create_thread, so an agent must infer the forum-vs-thread distinction.

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?

Gives useful prerequisite routing: fetch valid tag names via discord_list_forum_tags and read the forum's post guidelines from the forum topic via discord_list_channels. There is no explicit when-not-to-use guidance (e.g., use discord_create_thread for non-forum channels), which keeps it below a 5.

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

Deploy Server