WebhookTest.net

Configure webhook response

configure_webhook_response

Set the status, content type (JSON, plain text, XML, or form-encoded), body, optional Retry-After or X-Hook-Secret header, and a delay up to 10 seconds returned by the webhook endpoint. Browser visits always receive plain text.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	Yes
`status`	Yes
`headers`	No	optional response headers; only Retry-After and X-Hook-Secret are supported, matched case-insensitively
`delay_ms`	No	response delay in milliseconds, from 0 to 10000
`bucket_id`	Yes
`content_type`	Yes	application/json, text/plain, application/xml, text/xml, application/soap+xml, application/problem+xml, application/x-www-form-urlencoded, or application/*+json; only a charset parameter is allowed; empty selects application/json

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 29, 2026

addedInput schema / properties / content_type / description

Added value: +"application/json, text/plain, application/xml, text/xml, application/soap+xml, application/problem+xml, application/x-www-form-urlencoded, or application/*+json; only a charset parameter is allowed; empty selects application/json"

changedInput schema / properties / headers / description

Previous value: -"optional response headers; server-managed and hop-by-hop headers are rejected"New value: +"optional response headers; only Retry-After and X-Hook-Secret are supported, matched case-insensitively"

Changed2 schema fields changedAug 3, 2026

addedInput schema / properties / delay_ms

Added value: +{
+  "description": "response delay in milliseconds, from 0 to 10000",
+  "type": "integer"
+}

addedInput schema / properties / headers

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "optional response headers; server-managed and hop-by-hop headers are rejected",
+  "type": "object"
+}

First observedAug 3, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations cover the safety profile (non-readonly, non-destructive, non-idempotent, closed-world), and the description adds real behavioral constraints beyond them: a 10-second delay cap, only Retry-After/X-Hook-Secret headers being honored, and the override that browser visits always get plain text. It still omits permissions/scope needed and whether the configuration replaces all prior settings.

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

Conciseness4/5

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

Front-loaded with the verb and packed with relevant detail in one dense sentence plus a short qualifier about browser visits. No filler, though the first sentence is long and could be scannable if split.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation, and the description covers the behavioral edge cases (header whitelist, delay limit, browser fallback) for a mutation tool. It is slightly short on operational context such as auth requirements and the scope/lifetime of the configured response.

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?

With only 50% schema description coverage, the description compensates by naming status, content type (with the JSON/plain text/XML/form-encoded families), body, headers, and the delay bound, matching five of the six parameters. Only bucket_id is left implicit, and the description restates the schema's 10s cap consistent with delay_ms's own description.

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

Purpose4/5

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

Specific verb (Set) plus the exact resource being configured (the response returned by a webhook endpoint), with the settable fields enumerated. It does not explicitly name or contrast any sibling tool, so an agent must infer that this configures a response rather than managing the bucket/webhook itself.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives such as create_webhook_bucket or wait_for_webhook, and no stated prerequisites (e.g., that a bucket must already exist). Usage is only implied by the phrase 'returned by the webhook endpoint'.

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?