Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_thread_members

Read-only

Retrieve members of a Discord thread by channel ID, with optional pagination, result limits, and member details. Use it to inspect who participates in or can access a thread.

Instructions

List Thread Members. [GET /channels/{channel_id}/thread-members]

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

Input Schema

NameRequiredDescriptionDefault
afterNoReturn items after this ID (pagination)
limitNoMax results
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
with_memberNowith member

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds essentially nothing beyond that: no pagination behavior, no default limit, no auth requirements, no note about whether thread members differ from channel members.

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 fragments with zero waste; the endpoint path is front-loaded and the resource name leads. It's terse to the point of under-specification, but nothing is redundant.

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 list tool with pagination, a boolean modifier, and no output schema, the agent needs to know return shape and pagination semantics. The description supplies neither, leaving the schema and annotations to carry nearly everything.

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 all four parameters are documented in the schema, making 3 the baseline. The description adds no extra meaning about pagination semantics or what with_member actually returns.

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 states a specific verb+resource ("List Thread Members") and even names the REST endpoint. It doesn't differentiate from siblings like get_thread_member, list_voice_members, or list_guild_members, but the resource scope 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no exclusions, no mention of alternatives. The endpoint path implies the channel_id scope but the agent gets no hint about when to pick this over get_thread_member or other member-listing tools.

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