mcp-github-enterprise

List runner groups

list_runner_groups

Read-onlyIdempotent

Lists an organization's self-hosted runner groups and the repositories allowed to use them, so you can verify runner isolation and access scope.

Instructions

List the organization's self-hosted runner groups and which repositories may use them (runner isolation).

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

Input Schema

Name	Required	Description	Default
`org`	Yes	Organization login (must be within GHE_ORG_ALLOWLIST when that is set)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and repeatability are covered. The description adds that the response includes repository-to-group visibility ('which repositories may use them'), which is genuinely new behavioral information, but says nothing about pagination, sorting, or scope limits of the listing.

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?

One sentence, front-loaded with the resource being listed and followed immediately by the useful payload detail. No redundant restatement of the title beyond the necessary verb+resource. The trailing parenthetical '(runner isolation)' is a slightly cryptic gloss but still earns its place as framing.

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 single-parameter read-only list operation with no output schema and full schema coverage, the definition covers purpose, scope, and the key returned relationship. The main remaining gap is knowing what to do when the org is outside the allowlist or the list is empty, which is minor here.

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?

There is a single parameter with 100% schema description coverage, including the GHE_ORG_ALLOWLIST constraint, so the schema carries the semantics. The description adds no further meaning about the 'org' parameter (format, case sensitivity, allowlist failure behavior), which is acceptable at this coverage level but not additive.

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 ('List') and resource ('organization's self-hosted runner groups'), plus the payload detail that matters — which repositories may use each group. This implicitly separates it from the sibling list_self_hosted_runners (individual runners vs. groups), though the distinction is never stated outright.

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: an agent can infer 'use this to inspect runner-group isolation', but there is no explicit when-to-use guidance, no mention of prerequisites or permissions, and no named alternative (e.g., list_self_hosted_runners) for the adjacent question.

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