Skip to main content
Glama
Upload-Post

Upload-Post

Official

List webhook subscriptions

list_webhook_subscriptions
Read-only

List an account's extra webhook destinations, newest first, with status and health filters. Use it to find a subscription_id or check which endpoints are active.

Instructions

The account's webhook subscriptions: extra destinations (an n8n trigger, a REST hook…) that receive the listed events besides the account webhook, newest first, active and disabled, with limit (at most 10 active) and active_count. Each one has id, url, events, profile_username (null = every profile), source, name, status active|disabled, disabled_reason (endpoint_gone, failing_too_long, blocked_url, profile_removed), last_delivery_at and health (consecutive_failures, last_failure). With subscription_id it returns just that one. To see what was sent to a subscription use list_webhook_deliveries. Not generally available yet: until webhook subscriptions are switched on for the account, every call answers 503 with reason webhook_subscriptions_disabled (the feature is off, not a temporary failure).

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

Input Schema

NameRequiredDescriptionDefault
urlNoOnly subscriptions to exactly this URL.
sourceNoOnly subscriptions with this source label, e.g. 'n8n'.
statusNoOnly active or only disabled subscriptions.
subscription_idNoSubscription id (`whsub_...`) from list_webhook_subscriptions or create_webhook_subscription.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint/destructiveHint=false, the description discloses ordering ('newest first'), scope ('active and disabled'), result caps ('at most 10 active'), the meaning of disabled_reason values, health fields, and profile_username null semantics. Most importantly it pre-announces the 503 + webhook_subscriptions_disabled behavior as a feature flag rather than a transient failure, which is exactly the kind of context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scoping and the departure point for list_webhook_deliveries are front-loaded, which is good. However, the long mid-section enumerating every return field (id, url, events, profile_username, source, name, status, disabled_reason values, last_delivery_at, health) is largely redundant given an output schema exists, and the run-on sentence structure makes it harder to scan than it needs to be.

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 read-only filtered list with a full output schema and complete annotation coverage, nothing material is missing: scope, ordering, filters, single-item mode, the 10-active limit, and the 503 feature-flag caveat are all stated. An agent could call this correctly without opening any other field.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: subscription_id is described functionally ('it returns just that one'), and status/limit are tied to the notion of active versus disabled subscriptions. The url and source filters are left entirely to the schema, which is acceptable given full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition states a specific verb and resource up front ('The account's webhook subscriptions') and immediately scopes it as 'extra destinations... besides the account webhook', which distinguishes it from the account-level webhook tooling. It also explicitly names the sibling that serves a different question ('To see what was sent to a subscription use list_webhook_deliveries').

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear routing rule to list_webhook_deliveries for delivery history, and explains that passing subscription_id narrows the call to a single record. It also warns that until the feature is enabled every call returns 503 webhook_subscriptions_disabled, which prevents misinterpretation as an outage. It does not fully cover when to prefer this list over, say, create/delete flows, but the core when-to-use guidance is explicit.

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

Deploy Server

Other Tools