List webhook subscriptions registered to your API key. Use page and per_page to control pagination.
GET /api/v1/webhooks — list webhook subscriptions registered for the current API key
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based) | |
| per_page | No | Items per page (max 100) |
Changes observed during successful MCP inspections.
v0.0.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations available, the description carries the responsibility for behavioral disclosure. It does communicate GET semantics and API-key scoping, which is useful, but it does not mention pagination defaults, ordering, or whether the list includes only active webhook subscriptions.
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?
The description is a single concise sentence that front-loads the HTTP method, endpoint, resource, and scope. Every word earns its place with no redundant filler.
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 simple two-parameter list endpoint with fully documented parametersage, this description is mostly complete. The only notable gap is the lack of detail about the response shape or default pagination behavior, but this is a low-complexity tool.
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?
Both parameters are fully described in the input schema, so schema coverage is 100%. The description adds no extra parameter-level meaning, making the baseline score of 3 appropriate.
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 states a clear action and resource: 'list webhook subscriptions' for the current API key. It is distinct enough from siblings like webhooks_create or webhooks_events, though it does not explicitly contrast with beaconed_webhooks_get.
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?
No guidance is provided about when to use this tool versus alternatives such as beaconed_webhooks_get or beaconed_webhooks_events. The context is implied by the word 'list,' but there is no explicit routing or exclusionary guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.