Page Lemon

Add an app webhook

add_app_webhook

Destructive

Adds a signed app-event webhook, ids only. Two-step. Returns id and test; the signing secret is given in the Dashboard only.

Input Schema

Name	Required	Description
`url`	Yes	https:// address
`site`	Yes
`events`	No	default all; e.g. row.created, member.joined
`confirm_token`	No

Output Schema

Name	Required	Description	Default
`events`	No
`url_host`	No
`agent_message`	No
`confirm_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 27, 2026
- addedOutput schema / properties / agent_message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / events
```
Added value: +{
+  "type": "array"
+}
```
- addedOutput schema / properties / url_host
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedOct 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "confirm_token": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 25, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare the safety profile (destructiveHint=true, openWorldHint=true, non-idempotent), and the description adds genuinely new context: the webhook is signed, the signing secret is never returned by the API (Dashboard only), and the operation is a two-step flow. It stops short of explaining what happens to existing webhooks or what the intermediate step returns.

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?

Three short, front-loaded clauses with no filler; the verb and resource come first and the caveats follow. Density is high, though 'ids only' is terse to the point of ambiguity.

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

Completeness3/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 needn't be spelled out, and the destructive/open-world profile is covered by annotations. The unresolved gap is the two-step flow: the description names it but never explains how confirm_token is obtained or used, which is the one thing an agent must know to complete the call.

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 coverage is 50%: url and events are documented in-schema (including default-all and event name examples), while site and confirm_token are bare. The description partially compensates by implying site takes an ID ('ids only') and that confirm_token belongs to the two-step flow, but it never explains the token's origin or lifetime.

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?

States a specific verb and resource ('Adds a signed app-event webhook') and adds a distinguishing trait (signed events, ids only), so an agent can tell it apart from remove_app_webhook. The phrase 'ids only' is cryptic and could mean either input or output is ID-based, which blunts the precision slightly.

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?

'Two-step' combined with the confirm_token parameter implies a two-call confirmation flow, which is useful implied guidance. However, it never says when to prefer this over remove_app_webhook or other add_* siblings, nor what the first step actually requires or returns to trigger the second.

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

All Page Lemon tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?