Create a new post in a Discord forum channel with content, optional tags, and pinning to highlight important announcements.
Creates a new post in a Discord forum channel with optional tags
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | ||
| title | Yes | ||
| pinned | No | Pin the post to the top of the forum channel after creating it | |
| content | Yes | ||
| forumChannelId | Yes |
Changes observed during successful MCP inspections.
v1.5.0Input schema / properties / pinnedAdded value: +{
+ "description": "Pin the post to the top of the forum channel after creating it",
+ "type": "boolean"
+}v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description provides no information about side effects, required permissions, potential errors (e.g., invalid channel ID, existing post), or any other behavioral traits. With no annotations available, the description carries the full burden and fails to disclose these aspects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, succinct sentence with no unnecessary words. It directly conveys the tool's function and the optional nature of tags, making it easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the action, the description is adequate on a basic level, but it omits important context such as the requirement that the channel must be a forum channel, the need for valid tags, and potential failure modes. Without annotations or an output schema, this missing context leaves the description incomplete for robust decision-making.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 5 parameters, but only 'pinned' has a description. The description itself mentions 'optional tags', giving some context for that parameter, but it does not explain forumChannelId, title, or content. Schema coverage is low (20%), and the description does not compensate, leaving many parameters underspecified.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 tags feature. This distinguishes it from sibling tools like discord_update_forum_post or discord_reply_to_forum.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly state when to use this tool versus alternatives such as discord_reply_to_forum or discord_update_forum_post. However, the verb 'creates' implies that it is for new posts, so the usage is inferable but not explicitly guided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.