Skip to main content
Glama

discord_get_forum_post

Retrieve forum post details and messages from Discord using thread ID to access discussion content.

Instructions

Get a forum post's details and its messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYes
limitNoNumber of messages to fetch (1–100, default 20).

Implementation Reference

  • The 'discord_get_forum_post' handler function in src/tools/forums.ts, which fetches thread details and messages from Discord.
    case "discord_get_forum_post": {
      const thread = await getThreadChannel(args.thread_id as string);
      const limit = Math.min(Number(args.limit ?? 20), 100);
      const messages = await thread.messages.fetch({ limit });
      const result = {
        id: thread.id,
        name: thread.name,
        archived: thread.archived,
        locked: thread.locked,
        messageCount: thread.messageCount,
        appliedTags: thread.appliedTags,
        createdAt: thread.createdAt?.toISOString(),
        messages: [...messages.values()]
          .sort((a, b) => a.createdTimestamp - b.createdTimestamp)
          .map((m) => ({
            id: m.id,
            author: m.author.tag,
            content: m.content,
            timestamp: m.createdAt.toISOString(),
          })),
      };
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
    
    case "discord_list_forum_threads": {
      const forum = await getForumChannel(args.forum_channel_id as string);
      const active = await forum.threads.fetchActive();
      const archived = await forum.threads.fetchArchived();
      const threads = [
        ...active.threads.values(),
  • The input schema definition for 'discord_get_forum_post' which requires 'thread_id' and optional 'limit'.
    name: "discord_get_forum_post",
    description: "Get a forum post's details and its messages.",
    inputSchema: {
      type: "object",
      properties: {
        thread_id: { type: "string" },
        limit: { type: "number", description: "Number of messages to fetch (1–100, default 20)." },
      },
      required: ["thread_id"],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't specify permissions required, rate limits, pagination behavior, or error conditions. For a tool with no annotation coverage, this is a significant gap in transparency.

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, clear sentence with zero waste. It's front-loaded with the core purpose and efficiently conveys the tool's function without unnecessary elaboration.

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?

Given the tool's complexity (retrieving forum posts with messages), lack of annotations, and no output schema, the description is insufficient. It doesn't explain what 'details' include, how messages are formatted, or any behavioral aspects like error handling. For a tool with these contextual gaps, more completeness is needed.

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 50% (only 'limit' has a description). The description doesn't add any parameter details beyond what's in the schema—it doesn't explain what 'thread_id' represents or provide context for the 'limit' parameter. Since the schema covers half the parameters, the baseline score of 3 is appropriate, but the description fails to compensate for the undocumented 'thread_id'.

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 clearly states the tool's purpose: 'Get a forum post's details and its messages.' It specifies the verb ('Get') and resource ('forum post's details and its messages'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'discord_read_messages' or 'discord_list_forum_threads', which could provide similar retrieval functions.

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. It doesn't mention prerequisites, context (e.g., needing a specific forum channel), or compare it to siblings like 'discord_read_messages' or 'discord_list_forum_threads'. This leaves the agent without clear usage instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server