mcp-discord-bridge

list_members

Retrieve up to 1000 members from a Discord server by specifying its guild ID. Optionally set a member limit between 1 and 1000.

Instructions

List members in a Discord server (up to 1000)

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

Input Schema

Name	Required	Description	Default
`guild_id`	Yes
`limit`	No	Max members to return (1–1000, default 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 25, 2026

TDQS

B3.3/5.0

Behavior2/5

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

The description mentions a limit of 1000 members, which is a behavioral trait, but it does not disclose other crucial behaviors such as whether it is read-only, requires permissions, how pagination works, or what happens if the server has more than 1000 members. Since no annotations are provided, the description carries the full burden, and it is insufficient.

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?

The description is a single, concise sentence that immediately conveys the action and key constraint. No unnecessary words or repetition.

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?

Without output schema or annotations, the description leaves gaps: no mention of return format, error handling, permissions, or pagination beyond the limit. For a list tool with two parameters, it is minimally adequate but not fully informative.

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?

The schema description coverage is 50% (only 'limit' has a description). The description adds context that the tool lists 'up to 1000' members, which aligns with the limit parameter. However, it does not explain 'guild_id' beyond being a server identifier. Baseline is 3 given coverage, and the description provides moderate compensation.

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

Purpose5/5

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

The description clearly states the verb 'List', the resource 'members', and the context 'in a Discord server' with a constraint 'up to 1000'. It distinguishes well from sibling tools like get_member (single member) and ban_member (different action).

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., get_member for individual lookup, search_messages for messages). It does not mention when not to use it or any prerequisites.

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