Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List forum posts

list_forum_posts
Read-only

List posts in a Discord forum channel, optionally filtered by tag and including archived posts, to review and manage discussions.

Instructions

Posts in a forum, filterable by tag, optionally archived too.

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": "<forum>"
    },
    "name": "list_forum_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly posts carrying this tag.
forumYesForum channel name or ID.
guildNoGuild (server) name or ID. Omit to use the default guild.
include_archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds only that archived posts are optional, but says nothing about ordering, pagination, result limits, or the default for include_archived — meaningful gaps for a list operation.

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?

One short clause with no filler, and the tag/archived filters are front-loaded. It is terse to the point of being a fragment, but nothing is wasted.

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?

For a 4-parameter list tool with no output schema, the definition leaves out return shape, ordering, pagination, and the default behavior of include_archived and guild. An agent could invoke it but cannot predict what comes back or how much.

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 75%, with tag, forum and guild documented inline, so the schema carries most of the load. The description does add value for the one undocumented parameter by explaining that archived posts are included optionally, matching include_archived.

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

Purpose3/5

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

The fragment 'Posts in a forum' names the resource and implies a listing operation, and 'filterable by tag, optionally archived too' scopes it, so an agent can roughly tell it apart from the mutating forum_post siblings. However, it never states a verb ('list') and reads as a noun phrase rather than a definition of an action.

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?

There is no explicit when-to-use statement, no prerequisites, and no routing advice. Usage is only implied by the noun phrase 'Posts in a forum' — an agent must infer that this is the read path while create/update/delete/reply handle writes.

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

Deploy Server

Other Tools