gapify-mcp-server

Integrations: Delete an Integration Hook

gapify_delete_integration_hook

DestructiveIdempotent

Permanently deletes an integration hook from a Gapify account using its account and hook IDs, with confirmation required for this destructive action.

Instructions

Delete an Integration Hook [Integrations] DELETE /api/v1/accounts/{account_id}/integrations/hooks/{hook_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>",
      "hook_id": "<hook_id>"
    },
    "name": "gapify_delete_integration_hook"
  }
}

Input Schema

Name	Required	Description	Default
`hook_id`	Yes	The numeric ID of the integration hook
`account_id`	Yes	The numeric ID of the account

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds value beyond them: the required auth mechanism (User API key in the `api-access-token` header) and the permanence wording. It doesn't cover error/permission behavior, but the auth disclosure is genuine added context.

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-loads the action and endpoint, then layers auth and destructiveness notes concisely. The trailing multilingual/digit boilerplate is generic padding but not enough to derail the structure.

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?

For a two-param delete with no output schema, the description covers the essentials an agent needs to call it: identity, endpoint, auth, and destructiveness. Missing only permission/failure behavior, which is a minor gap here.

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 baseline is 3, but the description adds a relevant encoding nuance: IDs and numbers may be submitted with Persian or Arabic-Indic digits, which directly affects how the required hook_id/account_id values can be formatted.

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+resource ('Delete an Integration Hook') and pins it to the exact endpoint DELETE /integrations/hooks/{hook_id}, which cleanly separates it from the sibling create/update/list integration hook tools.

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?

It signals destructiveness ('this permanently deletes the resource'), which implies caution, but gives no explicit when-to-use-vs-alternatives guidance (e.g. prefer update_integration_hook to modify, delete only to remove permanently). Usage is implied rather than stated.

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

Deploy Server