@nightsquawktech/gohighlevel-mcp-server

Update GoHighLevel Custom Value

ghl_update_custom_value

Idempotent

Update a custom value for a GoHighLevel location. Provide the custom value ID, with optional name, value, and location override.

Instructions

Update a custom value from /locations/{locationId}/customValues/{id}. Write operation: do not run against live data without explicit approval.

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>"
    },
    "name": "ghl_update_custom_value"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`value`	No
`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/5.0

Behavior4/5

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

Annotations provide idempotentHint and destructiveHint false. Description adds 'Write operation' warning about live data, supplementing annotations without contradiction.

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?

Two concise, front-loaded sentences covering purpose and caution. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple update tool given annotations and sibling context. However, no output schema and limited description of underlying business logic or side effects.

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

Parameters2/5

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

Description adds zero parameter details beyond schema. Schema covers 60% of parameters with descriptions, but no additional context is provided for the remaining parameters or their usage.

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?

Description clearly states verb 'Update', resource 'custom value', and the endpoint path. Differentiates from sibling tools like create, delete, get, list for custom values.

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?

Explicitly says 'Write operation: do not run against live data without explicit approval', providing cautionary context. No direct comparison to alternatives but sibling list implies distinct usage.

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

Deploy Server