Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_webhook

Destructive

Deletes a registered webhook endpoint by ID, stopping future event notifications to that endpoint.

Instructions

Delete a registered webhook endpoint.

Args:
    endpoint_id: The endpoint ID returned by ``register_webhook``.

Once deleted, the endpoint will no longer receive event notifications.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "endpoint_id": "<endpoint_id>"
    },
    "name": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpoint_idYesThe endpoint ID returned by ``register_webhook``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / endpoint_id / description
      Added value: +"The endpoint ID returned by ``register_webhook``."
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds a genuine post-condition not present in any structured field: the endpoint will stop receiving event notifications after deletion. It stops short of stating irreversibility, error behavior, or whether existing queued deliveries are dropped.

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 action, followed by the parameter and the consequence. Slightly redundant because the Args block repeats the schema description word for word, but overall tight with no padded sentences.

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?

A single-parameter, non-open-world delete with no output schema; the description covers purpose, the parameter source, and the effect of deletion. Given the rich annotations, nothing critical is missing, though a note on idempotency or error on bad IDs would make it complete.

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 100% and the Args block restates the endpoint_id schema description verbatim ('The endpoint ID returned by register_webhook'), adding no format, validation, or lookup guidance. Baseline 3 is appropriate since the schema does the explanatory work.

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 ('Delete a registered webhook endpoint'), which is unambiguous and clearly distinct from register_webhook and list_webhooks. It does not explicitly contrast itself with siblings, but the destructive single-object framing makes the intent obvious.

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?

Usage is implied by the operation itself (removing an endpoint you no longer want), and the description names register_webhook as the origin of the ID. There is no explicit when-not guidance, no mention of list_webhooks for discovering IDs, and no note on what happens if the ID is unknown or already deleted.

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

Deploy Server

Other Tools