User Intuition

Delete Webhook by URL (Deprecated)

delete_webhook

Destructive

Deprecated compatibility tool. List webhooks, then use delete_webhook_by_id so deletion works through clients that omit DELETE request bodies. A repeated deletion returns 404.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hook_url`	Yes
`organization_id`	No	Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Webhook deletion acknowledgement.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / organization_id

Added value: +{
+  "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

Changed4 schema fields changedSep 30, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / result / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

First observedSep 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructive=true, idempotent=false, openWorld=true, so the safety profile is covered. The description adds real behavioral context beyond that: the deprecation status, why the alternative exists, and the concrete failure mode that a repeated deletion returns 404.

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 sentences, front-loaded with the deprecation status, then the replacement path, then the error behavior. No filler; each sentence carries information.

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, yet the description still flags the 404-on-repeat behavior that matters for a non-idempotent destructive call. The main residual gap is the undocumented hook_url parameter, which the schema also leaves bare.

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 50%: organization_id is documented in the schema, but hook_url carries no description anywhere. The description only hints that the hook URL can be obtained by listing webhooks, which gives partial semantics without adding format or matching details.

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?

The description establishes this as a deprecated deletion path and names the operation indirectly through the sibling it defers to (delete_webhook_by_id). The verb+resource is implied by the name/title rather than restated, but an agent can distinguish it from create_webhook, get_webhook, and delete_webhook_by_id.

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

Usage Guidelines4/5

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

It gives an explicit sequence ('List webhooks, then use delete_webhook_by_id') and the condition that selects the alternative: clients that omit DELETE request bodies. It does not state affirmatively when this legacy tool is still the right call, so it stops short of a full when/when-not pairing.

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

All User Intuition 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?