Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_thread_member

Read-only

Retrieve details for a specific user in a Discord thread by channel and user ID, with an option to include the associated member object.

Instructions

Get Thread Member. [GET /channels/{channel_id}/thread-members/{user_id}]

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>",
      "user_id": "<user_id>"
    },
    "name": "get_thread_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID
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.4/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 safety is covered. The description adds nothing beyond the endpoint path — no note on error behavior when the user is not a thread member, no auth/permission requirements, and no hint about what the with_member flag changes.

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?

It is short and front-loaded, so nothing is bloated. But the second sentence is a raw REST path that duplicates the name's information rather than earning its place with useful context.

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?

There is no output schema, so the description ideally would say what a thread member record contains and how with_member alters it; it does neither. For a simple read-only single-resource getter with fully documented params and annotations, it is minimally adequate.

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 the three parameters (including the vague "with member") are documented in the schema itself. The description adds no extra meaning, so baseline 3 applies; the opaque with_member semantics remain unexplained in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get Thread Member" essentially restates the tool name, and the bracketed HTTP path only confirms that it is a per-channel, per-user lookup. It never clarifies what a thread member is or how it differs from list_thread_members, add_thread_member or remove_thread_member.

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 at all: no exclusions, no mention of when to prefer list_thread_members for enumeration versus this single-member lookup. The agent must infer the routing decision from the 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