delete_webhook_bucketPermanently delete a bucket and all of its captures. Requires confirm=true.
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | Yes | must be true to perform this destructive action | |
| bucket_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| success | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, but the description adds context by stating 'Permanently delete' and 'all of its captures', which clarifies the irreversibility and scope. It also reinforces the confirm=true requirement, which is useful beyond the annotation.
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 sentence that is front-loaded with the core action and includes the key requirement (confirm=true). No wasted words.
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?
Given the simplicity of the operation and the presence of an output schema and annotations, the description covers the essential behavior. It could mention potential failure modes or prerequisites, but for a straightforward delete tool it is sufficiently complete.
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 coverage is 50% (confirm has a description, bucket_id does not). The description adds meaning for confirm by stating 'Requires confirm=true', but it does not explain bucket_id. This partially compensates for the missing schema description but leaves one parameter underexplained.
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 clearly states the action (delete), the resource (bucket), and the scope (all captures), which distinguishes it from sibling tools like create_webhook_bucket or list_webhooks. The verb 'delete' is specific and unambiguous.
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 description does not explicitly mention when to use this tool versus alternatives like clear_webhooks. However, the purpose is clear enough that an agent can infer this is for permanent deletion, but no exclusions or alternative guidance are provided.
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.
Tools are mostly distinct: bucket lifecycle (create/delete/get/list/clear), response configuration, and webhook capture reading (get/list/wait) each target clear operations. There is minor potential confusion between get_webhook_bucket (bucket settings) and get_webhook (a capture), and clear_webhooks vs delete_webhook_bucket both involve deletion, but descriptions differentiate them adequately.
Tools follow a consistent verb_noun pattern (create/delete/get/list/clear/configure/wait_for + webhook bucket or webhook). The pattern is mostly uniform snake_case with predictable verbs, though wait_for_webhook and configure_webhook_response deviate slightly from the simple get/list/create/delete set, and the 'webhooks' vs 'webhook_bucket' noun variation is somewhat mixed.
Eight tools is well within the ideal 3-15 range and every tool serves a distinct, meaningful purpose for a webhook testing service. The surface covers capture, bucket lifecycle, response configuration, and polling without redundancy or bloat.
The surface covers the full lifecycle: create/get/delete buckets, clear captures, configure responses, read/list/wait for captures. The main gap is an absent update capture or redaction toggle operation, but the core workflows for testing webhooks—configure, capture, inspect—are fully covered.