Skip to main content
Glama
agentisend

agentisend

Remove a webhook

delete_webhook
DestructiveIdempotent

Permanently remove a webhook endpoint to stop all deliveries and make its history unreachable. Use this for genuine removal, not for pausing or disabling.

Instructions

Purpose: remove an endpoint for good. Deliveries stop immediately and its history stops being reachable. NOT for: pausing one. Disabling keeps the endpoint and its secret; delete it when it is genuinely gone. Returns: the id and confirmation it is gone. Nothing is re-delivered elsewhere.

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": {
      "webhook_id": "<webhook_id>"
    },
    "name": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_idYesThe endpoint id from list_webhooks.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
idNoIdentifier.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
deletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, but the description adds the concrete consequences beyond them: deliveries stop immediately, history becomes unreachable, the secret is gone, and nothing is re-delivered elsewhere. That is exactly the extra context the lower bar for annotated tools asks for.

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 labeled clauses (Purpose / NOT for / Returns) with zero waste, and the destructive consequence is front-loaded. Every sentence earns its place by clarifying scope, exclusion, or outcome.

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?

For a destructive two-parameter tool, the description covers purpose, the key alternative, the irreversibility of the action, and the return shape (even though an output schema exists). Nothing needed to call it correctly is missing.

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 100%, so webhook_id and idempotency_key are fully documented in the schema itself (including the retry semantics for the idempotency key). The description adds no parameter-level detail, so the baseline 3 applies.

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?

States a specific verb and resource ('remove an endpoint for good') and immediately contrasts it with the nearest alternative behavior (pausing/disabling). An agent can distinguish this from create_webhook or list_webhooks without opening a schema.

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?

Explicit when-not guidance: 'NOT for: pausing one. Disabling keeps the endpoint and its secret; delete it when it is genuinely gone.' It names the alternative action and the condition that selects it, leaving nothing to inference.

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