Skip to main content
Glama

ADS Beast

list_webhooks

Read-only

Return the outbound webhook endpoints registered for this organization, the events each one receives and its current delivery state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoWebhooks per page.
offsetNoWebhooks to skip; use next_offset from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 value beyond that by disclosing what the response carries — the endpoints, the events each subscribes to, and the current delivery state — which is information an agent cannot get from the annotations. It omits pagination behavior, but the schema's offset description covers that.

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 no filler; every clause (org scope, endpoints, subscribed events, delivery state) conveys distinct information. Nothing is repeated from the title or annotations.

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 no output schema, the description is nearly complete: it covers scope and the shape of returned data. The only gap is that it never clarifies the boundary with list_webhook_events, which a reader might reasonably wonder about.

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 (limit, offset) are documented in the schema itself, including the next_offset paging hint. The description adds no additional meaning about paging or limits, so the baseline 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 names a specific verb ('Return') and resource ('outbound webhook endpoints registered for this organization') and even enumerates the payload contents (events received, current delivery state). It is not tautological with the title. It does not explicitly differentiate itself from the sibling list_webhook_events, so it stops short of a 5.

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: a read-only listing of org webhook registrations. There is no explicit statement of when to call this versus list_webhook_events or any other listing tool, and no prerequisites or exclusions. The org-scoping phrase gives a weak contextual cue but no routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.