gapify-mcp-server

Accounts: Delete an Account

gapify_platform_delete_account

DestructiveIdempotent

Permanently delete a Gapify account by numeric ID via the platform API; this destructive action cannot be undone.

Instructions

Delete an Account [Accounts] DELETE /platform/api/v1/accounts/{account_id} Auth: Platform app 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>"
    },
    "name": "gapify_platform_delete_account"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 20, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, so the description's 'Destructive: this permanently deletes the resource' is somewhat redundant but reinforces the consequence. It adds useful context about authentication (API key header) and input encoding (Persian/Arabic-Indic digits), which are not covered by annotations.

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?

The description is front-loaded with the core action and includes key details (endpoint, auth, destructiveness, encoding) in a compact form. The note about Persian/Arabic-Indic digits is relevant but could be seen as slightly tangential to a delete operation.

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 simple delete tool with one parameter and rich annotations, the description covers the essentials: endpoint, auth, destructive nature, and input encoding. It does not describe error behavior or response format, but with no output schema this is a minor gap.

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 the single parameter is fully documented in the schema. The description adds no additional semantics about account_id beyond noting that IDs may use Persian/Arabic-Indic digits, which is general input formatting rather than parameter-specific meaning.

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 (Delete) and resource (Account) and includes the HTTP method and endpoint. This clearly distinguishes it from sibling tools like create_account, get_account, and update_account.

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?

The description implies usage through the operation name and destructive warning, but provides no explicit guidance on when to use this tool versus alternatives (e.g., deactivating an account or deleting other resources). No when-not or alternative tools are mentioned.

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

Deploy Server