Discord MCP Extended

discord_create_forum_post

Create a new post in a Discord forum channel with optional tags.

Instructions

Creates a new post in a Discord forum channel with optional tags

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

Input Schema

Name	Required	Description	Default
`tags`	No
`title`	Yes
`content`	Yes
`forumChannelId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.4Aug 9, 2026

TDQS

B3.3/5.0

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 action but does not mention required permissions, authentication, potential side effects (e.g., making the post visible to members), or failure scenarios. This is a significant gap 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, concise sentence that conveys the core purpose without superfluous words. It is well-structured and front-loaded with the key information.

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?

The tool has 4 parameters, no output schema, and no annotations, yet the description is only a short clause. It omits important contextual details such as return behavior, error conditions, and prerequisites, making it insufficient for a complete agent understanding.

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

Parameters2/5

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

The input schema has 4 parameters with 0% description coverage, and the description only adds 'optional tags', which confirms tags is optional but leaves forumChannelId, title, and content semantically unexplained. The description adds minimal value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Creates'), the resource ('a new post in a Discord forum channel'), and the optional capability ('optional tags'). It distinguishes from sibling tools like discord_get_forum_post and discord_delete_forum_post by focusing on creation.

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 through the verb 'creates' but provides no explicit guidance on when to choose this over alternatives like discord_reply_to_forum, nor any exclusions or prerequisites. The intended context is inferable but not spelled out.

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