list_webhook_deliveriesList bounded delivery attempts, status codes, and coarse failure reasons without payloads.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| page_size | No | ||
| webhook_id | Yes | ||
| organization_id | No | Organization for this operation and billing. Use list_organizations to choose an active membership. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | Bounded webhook delivery attempts. |
Changes observed during successful MCP inspections.
Input schema / properties / organization_id / descriptionPrevious value: -"Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet."New value: +"Organization for this operation and billing. Use list_organizations to choose an active membership."Input schema / properties / organization_idAdded value: +{
+ "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+}Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / page / maximumAdded value: +9007199254740991Input schema / properties / webhook_id / patternAdded value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / properties / result / additionalPropertiesPrevious value: -trueNew value: +{}Output schema / properties / result / properties / attempts / items / additionalPropertiesPrevious value: -trueNew value: +{}Output schema / properties / result / properties / attempts / items / properties / duration_ms / maximumAdded value: +9007199254740991Output schema / properties / result / properties / attempts / items / properties / duration_ms / minimumAdded value: +-9007199254740991Output schema / properties / result / properties / attempts / items / properties / status_code / anyOfPrevious value: -[
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / result / properties / page / maximumAdded value: +9007199254740991Output schema / properties / result / properties / page / minimumAdded value: +-9007199254740991Output schema / properties / result / properties / page_size / maximumAdded value: +9007199254740991Output schema / properties / result / properties / page_size / minimumAdded value: +-9007199254740991Output schema / properties / result / properties / total_count / maximumAdded value: +9007199254740991Output schema / properties / result / properties / total_count / minimumAdded value: +-9007199254740991Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond them by clarifying that results are bounded and exclude payloads, and that failure reasons are coarse rather than detailed.
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?
A single, front-loaded sentence with no filler. Every word contributes to scope, return content, or behavioral expectations.
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?
The tool has an output schema and rich annotations, so the description needn't explain return shapes or safety. Still, it omits pagination guidance and required webhook_id context, leaving some operational gaps for a four-parameter listing 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?
Schema description coverage is only 25%, with only organization_id documented in the schema. The description does not explain the required webhook_id, nor does it clarify page/page_size pagination semantics, so it fails to compensate for the undocumented parameters.
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?
States a specific verb and resource (list delivery attempts) along with the returned data categories (status codes, coarse failure reasons). The phrase 'without payloads' helps distinguish it from fetching full delivery details, though it does not explicitly name a sibling alternative.
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?
Usage is implied for inspecting webhook delivery history, and 'without payloads' suggests a lighter-weight inspection use case. However, there is no explicit guidance on when to choose this over get_webhook, list_webhooks, or webhook testing tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.