mcp-discord-bridge

get_forum_post

Retrieve a Discord forum post and its messages by providing the thread ID. Optionally limit the number of messages fetched.

Instructions

Fetch a forum post and its messages

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": {
      "thread_id": "<thread_id>"
    },
    "name": "get_forum_post"
  }
}

Input Schema

Name	Required	Description	Default
`thread_id`	Yes	Forum post (thread) ID
`limit`	No	Number of messages to fetch (1–100, default 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 25, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description alone must convey behavioral traits. It only states the action without disclosing whether it is read-only, destructive, or any side effects. The name implies read access but this is not explicit.

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?

The description is a single concise sentence with no filler. It front-loads the verb and resource, making it easy to parse. It could be slightly improved by adding optional context, but it is compact.

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

Completeness3/5

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

The description covers the basic purpose but lacks details about the return format, whether messages are paginated, or any relationship between the post and its messages. Given no output schema, more context would be helpful, but the tool is simple.

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?

The input schema already has descriptions for both parameters (thread_id and limit), with 100% coverage. The tool description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 tool fetches a forum post and its messages. The verb 'fetch' combined with the resource 'forum post and its messages' is specific and distinguishable from sibling tools like create_forum_post or delete_forum_post.

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 such as get_channel_messages or list_threads. No context about prerequisites, limitations, or exclusion cases is given.

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