Skip to main content
Glama

Delete Webhook

delete_webhook
Destructive

Delete a registered webhook so Mobile Text Alerts stops sending its events to that URL. Use list_webhooks to find the id. Use this to clean up a webhook whose receiving URL has changed, or one that should not be receiving account events.

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

Input Schema

NameRequiredDescriptionDefault
webhookIdYesID of the webhook to delete, as returned by list_webhooks or register_webhook.

Output Schema

NameRequiredDescriptionDefault
dataYesRaw Mobile Text Alerts API response body. Currently null — a successful delete returns 204 No Content — so rely on `success` and `status`.
errorNo
statusYes
successYes
statusTextYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so safety is covered. The description adds genuine context beyond that by explaining what is destroyed: event delivery to the registered URL ceases. It does not state whether deletion is permanent or whether re-registration is required, which would have completed the picture.

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 are front-loaded with the action and its effect, then the id lookup, then the use case. Every sentence contributes, though the third sentence's two scenarios could be tightened into one clause.

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?

With one required parameter fully documented, an output schema, and annotations covering destructiveness, the description supplies exactly what remains: the consequence of deletion and how to source the id. Nothing an agent needs 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 coverage is 100% and the webhookId property already documents that it comes from list_webhooks or register_webhook, including the exclusiveMinimum constraint. The description's pointer to list_webhooks restates the schema rather than adding format or edge-case 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?

The description states a specific verb and resource ("Delete a registered webhook") and immediately names the concrete effect: Mobile Text Alerts stops sending events to that URL. This distinguishes it from register_webhook and list_webhooks without requiring the schema.

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 explicit when-to-use conditions (the receiving URL has changed, or the webhook should not be receiving account events) and points to list_webhooks to obtain the id. It lacks a stated when-not-to-use or a caution about confirming before permanent removal, so it falls short of full alternative/exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources