Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_role_members

Read-only

Retrieve member IDs assigned to a specified Discord server role, returning up to 100 results to identify which members hold that role.

Instructions

List member IDs that have a role (up to 100). [GET /guilds/{guild_id}/roles/{role_id}/member-ids]

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>",
      "role_id": "<role_id>"
    },
    "name": "list_guild_role_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_idYesRole ID
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 the meaningful detail that results are IDs only and capped at 100, but says nothing about whether truncation is signalled, how to page past the cap, or what permissions are needed.

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?

A single front-loaded sentence states the operation and the result cap, followed by a compact endpoint reference. Nothing is padded, though the bracketed REST path adds little for an agent that already has the schema.

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 simple two-required-parameter read with no output schema, the definition covers what is returned (IDs) and the size limit. It falls short on truncation behavior and permission requirements, which matter because silently receiving only 100 IDs could mislead an agent about role size.

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% and both parameters are documented ('Role ID', 'Server (guild) ID'), so the schema carries parameter meaning. The description only mirrors the path template and adds no format, type, or constraint detail beyond it.

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?

Specific verb 'List' plus a precisely scoped resource: member IDs holding a given role, with a stated cap of 100. That 'IDs only, by role' framing is what separates it from the bulk member-listing siblings, though no sibling is named explicitly.

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 statement of when to choose this over list_guild_members, query_guild_members, or search_guild_members, and no prerequisites or exclusions are given. The only contextual hint is the '(up to 100)' cap, which implicitly warns of truncation but is not framed as guidance.

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