gapify-mcp-server

Custom Attributes: Remove a custom attribute from account

gapify_remove_custom_attribute

DestructiveIdempotent

Permanently deletes a custom attribute definition from an account. Provide the account ID and attribute ID to remove it via the API.

Instructions

Remove a custom attribute from account [Custom Attributes] DELETE /api/v1/accounts/{account_id}/custom_attribute_definitions/{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>",
      "id": "<id>"
    },
    "name": "gapify_remove_custom_attribute"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The ID of the custom attribute to be deleted
`account_id`	Yes	The numeric ID of the account

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 20, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the 'permanently deletes' line largely repeats structured data. The added value is the auth requirement (User API key in api-access-token header), which the agent cannot get from annotations; the Persian/Arabic-Indic digits note is irrelevant to a delete operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and endpoint are front-loaded, which is good, but the trailing sentence about Persian/Farsi text values and Persian/Arabic-Indic digits is irrelevant filler for a deletion operation and dilutes the definition.

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 two-parameter destructive call with full annotation coverage and a complete schema, the description supplies enough: purpose, endpoint, auth method and irreversibility. No output schema exists, and none is expected for a delete.

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% and both parameters (id, account_id) are documented in the schema, so the schema carries the burden. The description adds no parameter-level detail beyond the path template, making baseline 3 appropriate.

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 ('Remove a custom attribute') and even names the exact HTTP operation (DELETE .../custom_attribute_definitions/{id}). This clearly distinguishes it from the sibling verbs list/add/get/update on the same resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never states when to use this tool versus the sibling add/update/get/list custom-attribute tools, nor any precondition for removal. Usage is only inferable from the verb 'Remove', so guidance is minimal.

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

Deploy Server