mcp-github-enterprise

List organization webhooks

list_webhooks

Read-onlyIdempotent

Lists an organization's webhooks and their subscribed events, redacting secrets so you can audit integrations without exposing credentials.

Instructions

List the organization's webhooks and their events. Webhook secrets are redacted and never returned.

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

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.8/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description earns credit by adding a non-obvious behavioral fact not present in any structured field: webhook secrets are redacted and never returned, which stops an agent from expecting or attempting to retrieve signing secrets. It does not mention pagination or result limits, which keeps it from a 5.

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?

Two short sentences with no filler. The primary capability is stated first and the redaction caveat follows, which is the correct front-loading order.

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 simple single-parameter, read-only list tool with full annotation coverage and no output schema, the description covers purpose and the one surprising behavior (redaction). The remaining gap is the return shape, such as whether results are paginated or how events are nested, which the description leaves entirely unspecified.

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 the only parameter (org) is already documented in the schema, including the GHE_ORG_ALLOWLIST constraint. The description adds no additional meaning about the org argument, so the baseline of 3 applies.

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?

The description states a specific verb and resource: it lists the organization's webhooks and their events. That is clear enough that an agent knows exactly what it returns. It stops short of a 5 only because there is no sibling tool (such as a get_webhook or list_repo_webhooks) to be explicitly distinguished from, so no comparative framing is offered.

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?

The scope is implied: this returns org-level webhooks only, which helps an agent avoid expecting repository-level hooks. However, there is no explicit when-to-use statement, no prerequisites (the required org and the GHE_ORG_ALLOWLIST constraint appear only in the schema), and no mention of alternatives for retrieving a single webhook.

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