discord-mcp

List forum posts

discord_list_posts

Read-only

List forum posts by recent activity, filtered by tags, title text, idle days, or status, with tag counts, to find active, stale, or archived discussions.

Instructions

List posts in a forum channel, most recently active first, with their tags. Filter by tag names (posts must carry all of them), a word in the title, or idle time (stale posts). Includes a count per tag. status: open (default), closed (archived) or all.

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_id": "<forum_id>"
    },
    "name": "discord_list_posts"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No	Only posts carrying all these tags (names)
`limit`	No
`status`	No		open
`forum_id`	Yes	Forum channel ID
`min_idle_days`	No	Only posts with no activity for at least this many days
`title_contains`	No	Case-insensitive text to match in the title

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuine behavior beyond that: result ordering by recent activity, the meaning of 'closed' as archived, the default status of open, and that tag counts are included in the response. It doesn't mention result size behavior or what the per-post payload looks like, keeping it below a 5.

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 short and front-loads the core action and ordering before enumerating filters. A few clauses are compressed into run-ons (the tag-count sentence interrupts the filter list), but no sentence is filler.

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

Completeness4/5

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

For a 6-parameter, read-only listing tool with no output schema, the definition covers the essentials: filtering dimensions, default status, ordering, and the fact that tag counts come back. It leaves paging/limit behavior implicit, which is the main gap but is partially recoverable from the schema.

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 coverage is 67%, and the description largely restates schema text — 'all these tags', title matching, idle days — while adding the useful framing of idle filtering as 'stale posts' and confirming status defaults. The limit parameter and its cap go unmentioned in the description, so it adds only marginal meaning over the schema.

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 gives a specific verb and resource ('List posts in a forum channel') plus the default ordering ('most recently active first') and return shape ('with their tags'), which is far more than the title restated. It doesn't explicitly distinguish itself from the sibling discord_list_forum_tags, and the phrase 'Includes a count per tag' could momentarily blur that line, so it falls short of a 5.

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?

Usage is implied rather than stated: the filter options (tags requiring all matches, title keyword, idle days, status) sketch the situations the tool serves, and the default 'open' is called out. There is no explicit when-to-use or when-not-to-use guidance and no named alternative for the closely related tag-listing sibling.

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

Deploy Server