Skip to main content
Glama
discord-mcp-lite

discord-mcp-lite

list_threads

Read-only

Retrieve a guild's active threads and, when a channel ID is supplied, its archived public threads to inspect Discord discussion history.

Instructions

List a guild's active threads, plus archived public threads when channel_id is given.

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": {
      "guild_id": "<guild_id>"
    },
    "name": "list_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesGuild id.
channel_idNoOptional: also list archived public threads of this channel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds real behavioral context beyond that: results are guild-wide by default, and archived results are limited to public threads of a single channel. It says nothing about pagination, result limits, or whether archived private threads exist at all.

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

Conciseness5/5

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

One sentence, front-loaded with the default behavior and then the conditional extension. There is no redundant or filler wording.

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 two-parameter read tool with full schema coverage and a readOnly annotation, the definition covers scope and the conditional mode adequately. The remaining gap is pagination/limit behavior, which is minor for a simple list endpoint.

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 100%, so both parameters are already documented. The description's main added value is clarifying that channel_id changes behavior (adds archived public threads) rather than merely filtering, which is a slight lift over the schema description. Otherwise it restates 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 ('List') and resource ('a guild's active threads') with clear scope, and it states the extra mode (archived public threads). It does not name a sibling to contrast with, but no sibling in the supplied list covers threads, so the purpose is unambiguous without that.

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 through the conditional: pass channel_id to extend the listing to archived public threads of that channel. There is no explicit when-to-use versus an alternative tool, and no note on when channel_id can or should be omitted other than 'Optional' in the schema.

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