Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_active_threads

Read-only

Retrieves all active threads visible in a Discord server so you can review ongoing conversations; provide the server ID to target the guild.

Instructions

List all active threads in a server that you can see. [GET /guilds/{guild_id}/threads/active]

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_guild_active_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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. The description adds one genuinely useful behavioral fact — results are filtered to what the caller "can see" (permission-scoped) — but says nothing about result volume, pagination, or whether thread members are included.

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 sentence with the core action front-loaded, followed by the REST path. The bracketed endpoint is developer metadata that doesn't help an agent decide or invoke, but it costs little.

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 one-parameter read tool with full annotation coverage and no output schema, the basics are present. What's missing is the differentiator an agent most needs: how this relates to the archived-thread and search siblings, and roughly what the response contains.

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?

With a single parameter at 100% schema coverage, the schema already explains guild_id as the server ID. The description adds nothing beyond that baseline, which is acceptable here rather than a defect.

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 and resource ("List all active threads in a server") plus the underlying endpoint, so an agent knows exactly what is returned. "Active" implicitly separates it from the archived-thread siblings, though the description never names them to make that distinction explicit.

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 or when-not-to-use guidance, and no alternative is named despite several sibling tools (list_public_archived_threads, list_joined_private_archived_threads, search_threads) that an agent could easily confuse with this one. The only usage signal is the implied "active only" scope in the phrase "active threads".

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