mcp-github-enterprise

List organization members

list_members

Read-onlyIdempotent

Lists an organization's members, optionally filtered by role (admin for owners, member for everyone else), to review access and membership.

Instructions

List an organization's members, optionally filtered by role (admin = owners, member = everyone else).

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": {
      "org": "<org>"
    },
    "name": "list_members"
  }
}

Input Schema

Name	Required	Description	Default
`org`	Yes	Organization login (must be within GHE_ORG_ALLOWLIST when that is set)
`role`	No	Filter by role; default all

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds only the role mapping, and says nothing about pagination, result size, or permission requirements beyond the schema's allowlist note.

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?

A single front-loaded sentence with the action, resource, and its only option. No filler, no repetition of the title, and the parenthetical is placed exactly where it is needed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only list tool with full schema coverage and complete annotations, this is nearly sufficient. The only meaningful gap is the absence of any hint about result volume or pagination behavior, which an agent would want before iterating over members.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: it defines what the enum values actually select ('admin = owners, member = everyone else'). That is a genuine clarification beyond 'Filter by role; default all', though the default and org allowlist behavior still come only from the schema.

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?

States a specific verb and resource ('List an organization's members') plus the available filter. It is clear in isolation, but unlike the strongest definitions it does not name a sibling to distinguish from, such as list_teams or list_security_managers, which also return people-like data within an org.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied by 'optionally filtered by role' — there is no explicit statement of when to call this versus list_security_managers or get_organization, and no mention of prerequisites. Adequate for a simple list tool but leaves routing to inference.

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