Formhaus Cloud

Get the webhook of a form

get_webhook

Read-only

Shows where the webhook of a form posts and whether deliveries succeed. The secret is masked; reveal_webhook_secret returns the full one and update_form_settings sets or removes the URL. Returns url, the masked secret and the last 100 deliveries with submission_id, attempt, status_code, error, duration_ms and created_at. Requires an account key (fh_live_...); agent keys answer owner_key_required.

Input Schema

Name	Required	Description	Default
`form_id`	Yes	The 10-character form_id returned by publish_form or list_forms, such as "abcDEF1234".
`reveal_secret`	No	Retired. Call reveal_webhook_secret for the full signing secret.

Output Schema

Name	Required	Description	Default
`url`	Yes
`secret`	Yes
`deliveries`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 17, 2026

addedOutput schema / properties / deliveries / items / properties / event_id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / deliveries / items / properties / trigger
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / deliveries / items / required

Previous value: -[
-  "submission_id",
-  "attempt",
-  "status_code",
-  "duration_ms",
-  "created_at"
-]New value: +[
+  "submission_id",
+  "event_id",
+  "trigger",
+  "attempt",
+  "status_code",
+  "duration_ms",
+  "created_at"
+]

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / form_id / description

Previous value: -"The form_id returned by publish_form or list_forms."New value: +"The 10-character form_id returned by publish_form or list_forms, such as \"abcDEF1234\"."

First observedOct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well past the readOnlyHint/idempotentHint annotations by disclosing the masking behavior of the secret, the auth requirement (account key fh_live_...) and the exact failure mode (agent keys answer owner_key_required). This is the kind of constraint an agent cannot infer from structured fields.

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 purpose with the sibling routing next; tight and waste-free. The enumerated return fields are somewhat redundant against the existing output schema, costing a little space.

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?

An output schema exists, so return values need not be spelled out, yet the description still covers purpose, masking semantics, tool alternatives and the auth precondition. Nothing needed to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: it explains that the secret is masked here and that the full value requires a different tool, which disambiguates the retired reveal_secret parameter and the boolean semantics of the call.

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?

Specific verb and resource (shows where a form's webhook posts and whether deliveries succeed), plus an explicit scope note that the secret is masked. It is cleanly distinguishable from reveal_webhook_secret and update_form_settings by name in the same breath.

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

Usage Guidelines5/5

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

It routes the agent explicitly: use reveal_webhook_secret for the full secret, use update_form_settings to set or remove the URL. The condition selecting each alternative is stated, not implied.

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

All Formhaus Cloud tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?