@nightsquawktech/gohighlevel-mcp-server

List GoHighLevel Custom Values

ghl_list_custom_values

Read-onlyIdempotent

List custom values for a GoHighLevel location, with pagination limit and offset, and select markdown or JSON output.

Instructions

List custom values for a GoHighLevel location from /locations/{locationId}/customValues.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ghl_list_custom_values"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of items to return from the local page.
`offset`	No	Number of items to skip locally after receiving the API response.
`location_id`	No	Optional GoHighLevel location ID override. Defaults to GHL_LOCATION_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

B3.3/5.0

Behavior3/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds the endpoint path but no further behavioral traits (e.g., pagination, rate limits, required permissions). It does not contradict annotations.

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 a single, concise sentence with no unnecessary words. It is efficiently front-loaded with the action and resource.

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?

Given the annotations and schema, the description provides the essential information but lacks context such as what custom values are, how they relate to custom fields, or typical response structure. The addition of response_format compensates partially, but completeness is adequate.

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?

All parameters have descriptions in the input schema (100% coverage). The description adds no extra meaning beyond the schema, so baseline score of 3 applies.

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

Purpose4/5

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

The description clearly states it lists custom values for a GoHighLevel location and provides the API endpoint. However, it does not explicitly distinguish this tool from sibling tools like ghl_list_custom_fields or ghl_get_custom_value, relying on the tool name for differentiation.

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?

No guidance is provided on when to use this tool versus alternatives such as ghl_get_custom_value (single value) or ghl_list_custom_fields (field definitions). The description lacks any context about appropriate use cases or when to avoid.

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

Deploy Server