simplepages

Stop forwarding leads to a webhook

remove_webhook

Remove a webhook from a page (pageId) or from a whole website (siteId) so leads stop being forwarded to it. The leads themselves are still captured and remain available via list_leads. A page cannot remove a webhook it inherits from its site; remove that one with siteId.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The webhook URL to remove (from list_webhooks).
`pageId`	No	Attach to a single page (id from list_pages). Give this or siteId.
`siteId`	No	Attach to a whole website, so every page in it forwards leads there (id from list_sites). Give this or pageId. Usually the right choice for a CRM or automation that should cover the whole website.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The stored URL that was removed.
`note`	Yes
`scope`	Yes	Whether this concerns one page or a whole website.
`pageId`	Yes	Set when scope is page.
`siteId`	Yes	Set when scope is site.
`removed`	Yes	Always true; a miss is an error result.
`remaining`	Yes

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation (false), the description explains side effects (leads remain captured) and the inheritance constraint, giving the agent a full understanding of what happens during removal.

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?

Three concise sentences cover purpose, side effects, and usage guidance without redundancy. The main action is stated first, and all additional info is relevant and compact.

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?

Given the optional parameters and subtle inheritance rule, the description is complete. It covers the action, the scope options, the side effect on leads, and the special case for inherited webhooks. No gaps remain.

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

Parameters5/5

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

While the schema already describes each parameter, the description adds critical nuance: the distinction between page-level and site-level removal and the rule that inherited webhooks require siteId. This goes beyond basic schema descriptions.

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?

Description clearly states the action (remove a webhook) and the target (page or website) with specific parameters. It distinguishes from sibling tools like add_webhook and list_webhooks by focusing on removal.

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?

Provides clear guidance on when to use pageId vs siteId, including the important rule that inherited webhooks must be removed via siteId. It also clarifies that removal does not delete leads, which helps set expectations.

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

All simplepages tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool has a distinct purpose, with clear differentiation between creating standalone pages vs. adding to sites, and separate analytics for pages, sites, and workspaces.

Naming Consistency4/5

Mostly follows verb_noun pattern, but uses both 'add' and 'create' for similar actions, and 'delete' vs 'remove' inconsistently.

Tool Count4/5

20 tools cover a broad range of functionality (pages, sites, redirects, scripts, webhooks, analytics, leads), which is reasonable but slightly on the higher side.

Completeness3/5

Covers CRUD for most entities, but lacks delete operations for pages, sites, scripts, and webhooks (except redirects), leaving notable gaps.

Resources

Need Help?