Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_public_archived_threads

Read-only

Lists public archived threads in a Discord channel with limit and before-based pagination, so you can review archived thread history.

Instructions

List Public Archived Threads. [GET /channels/{channel_id}/threads/archived/public]

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": {
      "channel_id": "<channel_id>"
    },
    "name": "list_public_archived_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
beforeNoReturn items before this ID (pagination) (ISO8601 time)
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered externally. The description's only added behavior cue is the endpoint path, which implies a channel-scoped read; it says nothing about ordering, pagination flow, or what an empty result means.

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?

Two short sentences, front-loaded with the action and followed by the route. Nothing is padded, though the endpoint bracket is more developer-facing than agent-facing.

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?

For a three-parameter read-only list operation with a fully documented schema and safety annotations, the definition is minimally sufficient. However, it omits anything about pagination behavior across the 'before' cursor and how the public/private archived distinction affects results, which would help an agent call it confidently.

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 100%, with limit, before (ISO8601/pagination) and channel_id all documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 description restates the tool name verbatim ('List Public Archived Threads') and adds only the REST endpoint path. It confirms this is a listing of archived public threads scoped to a channel, but it offers no distinguishing statement against siblings like list_private_archived_threads or list_guild_active_threads, leaving the agent to infer the difference from the name alone.

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 when-to-use guidance, no prerequisites (e.g., permission to view archived threads), and no named alternative for retrieving private or active threads. The agent must already know the ecosystem to route correctly among the archived/active thread siblings.

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