Skip to main content
Glama

List webhooks

list_webhooks
Read-onlyIdempotent

The user's webhooks, newest first: where each sends (its host; the full address is never shown), whether it is active, paused (and why) or waiting for the user's confirmation, its filters, and how many deliveries it completed this month. Each carries the link to its page in Werify.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
webhooksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description earns credit for adding behavior the annotations cannot convey: only the host is exposed and the full address is never shown, records can be paused with a reason or awaiting user confirmation, delivery counts are month-scoped, and each item carries a link to its Werify page.

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 dense sentence that front-loads the resource and ordering, then parenthetically details each field. Every clause carries real information, though the nested parentheses ("its host; the full address is never shown", "and why") make it slightly heavy to parse at a glance.

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

Completeness5/5

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

For a no-parameter read tool whose annotations cover the safety profile and which ships an output schema, this is complete: an agent knows what comes back, in what order, what each item's status and filter fields mean, and that the webhook URL is deliberately truncated. Nothing needed to call it correctly is missing.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline applies. The schema is an empty object, consistent with the definition.

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?

Names a specific verb and resource ("The user's webhooks") and immediately scopes the result set with ordering ("newest first") and the exact fields returned. It is not explicitly differentiated from list_webhook_deliveries or create_webhook, but the enumeration of status and delivery-count fields makes the read/listing role unmistakable.

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 implied by the shape of the tool — a zero-parameter listing of the user's own webhooks — rather than stated. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to list_webhook_deliveries for per-delivery detail or to create_webhook for adding one.

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.

Resources