Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_list_threads

List active or archived threads in a Discord channel to review ongoing or closed conversations, with a configurable result limit for scanning channel activity.

Instructions

List active or archived threads of a channel.

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": {
      "channelId": "<channelId>"
    },
    "name": "discord_list_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
archivedNo
channelIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether archived threads require extra permissions, whether results are paginated or ordered, what happens when archived=false, or what the returned items look like — significant gaps for a list tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is part of why behavioral detail is missing.

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?

With three parameters, no annotations, no output schema, and two undocumented parameters, the description is too thin. It should at minimum cover pagination via limit and the effect of the archived flag to be sufficient for correct invocation.

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 only 33%: only channelId is documented (as a snowflake). The description's 'active or archived' wording does explain the purpose of the archived boolean, but limit remains undocumented in both schema and description — no paging semantics or cap behavior is conveyed.

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 (List) and resource (threads) scoped to a channel, which clearly separates it from siblings like discord_create_thread or discord_archive_thread. It stops short of stating the return shape or ordering, but the operation itself is unambiguous.

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?

The phrase 'active or archived' implies the archived toggle exists, giving implicit guidance on how to reach each mode. It never says when to prefer this over related tools or what preconditions apply (e.g. thread-capable channel, permissions), so usage is inferred rather than stated.

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