List all registered webhook subscriptions with their event type, webhook URL, and creation date. Use this to review or verify which webhooks are currently active.
List all currently registered webhook subscriptions (id, event_type, webhook_url, created_at).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.13.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations present, the description carries the full burden. It accurately signals a read-only listing behavior and discloses the returned fields, but it does not mention potential edge cases such as empty results, ordering, authentication requirements, or pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One tightly scoped sentence states the action, the resource, and the return fields with no wasted words. The most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only listing tool, the description is essentially complete: it names the resource, the scope, and the fields returned. Minor omissions like response container format and error behavior do not meaningfully impair a correct call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters, so the baseline is 4 per the rubric. The description appropriately adds no parameter-level details because there are none to document.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and a specific resource ('currently registered webhook subscriptions'), and enumerates the exact fields returned. It clearly distinguishes the read-only listing role from mutation siblings like subscribe and unsubscribe.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'currently registered' makes the intended use clear: retrieve the existing set of webhook subscriptions. It does not explicitly name alternatives or exclusion conditions, but for a zero-parameter listing tool the context is unmistakable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.