Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_private_archived_threads

Read-only

Retrieve private archived threads from a Discord channel, with pagination and result limits, to review or manage archived discussions.

Instructions

List Private Archived Threads. [GET /channels/{channel_id}/threads/archived/private]

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_private_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.8/5.0
Behavior2/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. Beyond that, the description contributes only the endpoint path, which restates the name; it says nothing about permission requirements, pagination direction, or result ordering that would change how an agent invokes it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only two fragments and is front-loaded with the operation, but the bracketed route mostly duplicates the name rather than adding information. It is not verbose, yet the space it uses could have carried sibling differentiation or prerequisite detail.

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 paginated listing tool with no output schema and access-restricted semantics, the description never explains what comes back, how the cursor behaves, or what permissions are needed. Key information an agent needs to call it correctly is absent.

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%, so all three parameters (channel_id, limit, before) are already documented, including that 'before' is an ISO8601 pagination cursor. Baseline 3 is appropriate because the description adds no additional parameter meaning.

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?

States a specific verb and resource ('List Private Archived Threads') and reinforces it with the REST route GET /channels/{channel_id}/threads/archived/private. However, it never distinguishes this from very similar siblings such as list_public_archived_threads or list_joined_private_archived_threads, so an agent must guess which of the three archived-thread lister to call.

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 stated prerequisites (listing private archived threads typically requires elevated channel permissions), and no mention of when to prefer the public or joined-private variants. The agent is left to infer the selection rule from the tool name alone.

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