discord-server-mcp

create_forum_post

Creates a post in a Discord forum or media channel with tags, embeds, files, and link buttons, so you can publish structured content in one step.

Instructions

Create a post in a forum or media channel, with tags, embeds, files and link buttons.

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": "<forum>",
      "title": "<title>"
    },
    "name": "create_forum_post"
  }
}

Input Schema

Name	Required	Description
`bot`	No	Use this bot (name or id) instead of choosing automatically
`tags`	No	Tag names that exist in the forum
`files`	No
`forum`	Yes
`title`	Yes
`embeds`	No
`server`	No	Server name or id. Optional when the bot is in one server or DISCORD_GUILD_ID is set.
`content`	No
`dry_run`	No	Show the requests that would be made without changing anything
`link_buttons`	No
`slowmode_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations only declare readOnlyHint=false, so the description carries almost the full behavioral burden and does not meet it. It never says the post is immediately public, what permissions the bot needs, whether posting fails on missing tags, or that dry_run exists as a safe preview - even though dry_run is one of the most important behavioral signals 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.

Conciseness4/5

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

A single front-loaded sentence with a clear verb and resource, and no redundant restatement. It is arguably too terse given the tool's breadth, but nothing in it is wasted.

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?

With 11 parameters, deeply nested embed objects, and no output schema, this is a complex mutation tool that needs more than one sentence. The description omits dry_run, server/bot resolution behavior, and slowmode, leaving the agent dependent on the schema alone for half the surface.

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 only 36%, but the description names the headline optional inputs (tags, embeds, files, link buttons), which maps to the highest-value parameters. It is silent on slowmode_seconds, server, bot, and particularly dry_run, so it only partially compensates for the coverage gap.

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 (create a post in a forum or media channel) and enumerates the optional feature set it supports. It does not distinguish this tool from close siblings such as create_thread or set_forum_tags, so an agent cannot tell purely from the text which one fits a given posting scenario.

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 'forum or media channel' phrasing implies the target context, but there is no explicit when-to-use, when-not-to-use, or prerequisite guidance. Nothing says whether the bot must already be in the server, whether the forum must exist, or why an agent would pick this over create_thread.

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