@nightsquawktech/gohighlevel-mcp-server

Delete GoHighLevel Custom Value

ghl_delete_custom_value

Destructive

Deletes a custom value from a specified location in GoHighLevel. Confirmation must be set to true for the operation to proceed.

Instructions

Delete a custom value from /locations/{locationId}/customValues/{id}. Requires confirm: true and owner approval before live execution.

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": {
      "custom_value_id": "<custom_value_id>",
      "confirm": "<confirm>"
    },
    "name": "ghl_delete_custom_value"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	Yes	Required for destructive tools. The API call is made only when confirm is explicitly true.
`location_id`	No	Optional GoHighLevel location ID override. Defaults to GHL_LOCATION_ID.
`custom_value_id`	Yes	Custom value ID.
`response_format`	No	Output format: markdown for human-readable summaries, json for structured output.	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description adds important behavioral context beyond annotations: it requires confirm=true and owner approval before live execution. Annotations only indicate destructiveHint=true, so this is a valuable addition.

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 concise, consisting of two sentences that first state the action and resource, then list the safety requirements. No superfluous information.

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?

While the description covers the action and safety requirements, it does not describe the return value or what happens after deletion. Given the absence of an output schema, a brief note on the response would improve completeness.

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?

The input schema already provides descriptions for all 4 parameters (100% coverage). The description does not add new semantic details about the parameters beyond what the schema states.

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 clearly states the action ('Delete') and the resource ('custom value') with the endpoint URL, distinguishing it from other delete tools like ghl_delete_custom_field or ghl_delete_contact.

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 explicitly requires confirm=true and owner approval, providing clear usage constraints. However, it does not specify when to use this tool versus alternatives (e.g., ghl_delete_custom_field).

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

Deploy Server