gapify-mcp-server

Webhooks: Delete a webhook

gapify_delete_webhook

DestructiveIdempotent

Permanently deletes a webhook from a Gapify account using the account ID and webhook ID, removing its event delivery configuration.

Instructions

Delete a webhook from the account [Webhooks] DELETE /api/v1/accounts/{account_id}/webhooks/{webhook_id} Auth: User API key (header api-access-token). Destructive: this permanently deletes the resource. Text values may be written in Persian (Farsi) or any other language and are sent unchanged; IDs, numbers and phone numbers may use Persian or Arabic-Indic digits.

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

Input Schema

Name	Required	Description	Default
`account_id`	Yes	The numeric ID of the account
`webhook_id`	Yes	The numeric ID of the webhook

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds useful context beyond annotations by specifying the required auth header and noting that Persian/Arabic-Indic digits may be used, while also reinforcing permanence.

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?

The description is front-loaded with the action and resource, then quickly covers endpoint, auth, destructive behavior, and language/digit handling. Every line adds operational value with no filler.

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 two-parameter destructive delete with rich annotations and no output schema, the description provides everything needed: purpose, auth, endpoint, permanence, and input-format caveat. There is no meaningful missing context for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the two required ID parameters are already documented. The description adds useful format guidance that IDs and numbers may use Persian or Arabic-Indic digits, which is directly relevant to account_id and webhook_id.

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 webhook from the account," and the endpoint confirms the exact scope. It is clearly distinguishable from sibling tools such as gapify_list_webhooks, gapify_add_webhook, and gapify_update_webhook.

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?

The description gives clear context for using this tool and explicitly warns that the operation permanently deletes the resource. It does not explicitly name alternatives or when-not-to-use guidance, but the delete-specific purpose makes the selection obvious among siblings.

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

Deploy Server