Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_invite_friend_members

Read-only

List friend members for a Discord invite code or full invite link to identify who is associated with that invite.

Instructions

List Invite Friend Members. [GET /invites/{invite_code}/friend-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": {
      "invite_code": "<invite_code>"
    },
    "name": "list_invite_friend_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
invite_codeYesInvite code or full invite link (discord.gg/xyz)

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, openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the endpoint path — notably it never clarifies whether "friend members" means the caller's friends inside the invited guild, the invite creator's friends, or something else, which is the key behavioral ambiguity here.

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 padding and the resource identified up front. Brevity here comes from omission rather than tight writing, but there is no bloat to penalize.

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 single-parameter read tool the schema and annotations carry most of the load, but the description leaves the core concept (what constitutes a friend member) undefined and gives no sense of the returned collection. Given the crowded invite/member sibling space, that gap matters.

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% and invite_code already documents that a full invite link (discord.gg/xyz) is accepted. The description contributes only that the code is a path segment; no extra validation, format, or fallback detail is added, so the baseline 3 applies.

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?

"List Invite Friend Members" restates the tool name and adds only the HTTP path [GET /invites/{invite_code}/friend-members]. That path hints the resource is scoped under an invite, but the description never says what a "friend member" actually is or how this differs from get_invite or list_guild_members.

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, no prerequisite or permission note, and no mention of alternatives among the many sibling invite/member list tools. The reader must infer usage entirely from the name and endpoint.

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