Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_location_update_custom_value

Idempotent

Updates an existing location custom value by ID, letting you change its name and value through the GoHighLevel API.

Instructions

Update Custom Value Endpoint: PUT /locations/{locationId}/customValues/{id} (Version header: v3; source: v3/locations-v3.json)

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": {
      "locationId": "<locationId>",
      "id": "<id>",
      "body": "<body>"
    },
    "name": "ghl_location_update_custom_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCustom Value Id
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"customValuesDTO"
  2. First observedv2.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful API metadata (PUT method, v3 version header, spec source) but does not say whether the body replaces or merges fields, what the response looks like, or what permissions are required, so it adds only modest value beyond the 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?

Two short lines, with the action front-loaded and API details second. The 'source: v3/locations-v3.json' provenance note is low-value clutter but the rest is tight.

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?

For a 3-parameter nested-body mutation with annotations but no output schema, the description covers the endpoint and version but omits return behavior and whether the body is a full replacement. With schema coverage at 100% most calling details are available elsewhere, so this is adequate but incomplete.

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 parameters are already documented; the baseline is 3. The endpoint string does implicitly map locationId and id to the path and body to the request payload, which is a small semantic contribution, but the required name/value fields and update semantics are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Update Custom Value' and gives the endpoint PUT /locations/{locationId}/customValues/{id}, so the verb and resource are identifiable. However, it does not elaborate beyond the name/title or distinguish this from siblings such as ghl_location_create_custom_value, ghl_location_get_custom_value, or ghl_custom_field_update, so it sits at minimum-viable clarity rather than a clear 4.

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?

There is no statement of when to use this tool versus the create/get/delete custom-value siblings, and no prerequisites or exclusions are mentioned. The agent must infer usage entirely from the tool name.

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

Deploy Server

Other Tools