WebhookTest.net

Create webhook bucket

create_webhook_bucket

Create an anonymous temporary webhook capture bucket. The returned bucket ID is a bearer capability and expires after 15 days of inactivity.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	optional display name for the bucket
`controlled_test`	No	set true only for maintainer QA or automated evaluations; not for a real user's first test

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`name`	No
`error`	No
`dashboard_url`	No
`webhook_endpoint`	No
`inactivity_policy`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedInput schema / properties / controlled_test

Added value: +{
+  "description": "set true only for maintainer QA or automated evaluations; not for a real user's first test",
+  "type": "boolean"
+}

First observedAug 3, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that the returned bucket ID is a bearer capability and that the bucket expires after 15 days of inactivity. This adds meaningful auth and lifecycle context that annotations do not provide.

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

Conciseness5/5

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

Two concise sentences with no wasted words. The main behavior is front-loaded, and the security/expiry caveat is stated immediately after.

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 simple create operation with two optional parameters and an output schema, the description covers the essential semantics: anonymous creation, temporary nature, bearer capability, and expiry. Nothing needed for correct invocation appears missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameters are already fully documented. The tool description adds no additional parameter-level meaning, making baseline 3 appropriate.

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 description uses a specific verb and resource: 'Create an anonymous temporary webhook capture bucket.' It clearly distinguishes itself from sibling get/list/delete/clear operations by focusing on creation of a new bucket.

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

Usage Guidelines3/5

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

The description implies the appropriate use case through 'anonymous temporary webhook capture bucket', but it does not explicitly state when to prefer this tool over alternatives or mention exclusions. Sibling tools are not referenced for routing.

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

All WebhookTest.net tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?