Skip to main content
Glama
Sign In
@nightsquawktech/gohighlevel-mcp-server

@nightsquawktech/gohighlevel-mcp-server

by NightSquawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get GoHighLevel Custom Field

ghl_get_custom_field
Read-onlyIdempotent

Retrieve a specific custom field by ID from a GoHighLevel location, with optional location override and output format selection.

Instructions

Get one custom field for a GoHighLevel location from /locations/{locationId}/customFields/{id}.

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": {
      "field_id": "<field_id>"
    },
    "name": "ghl_get_custom_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
field_idYesCustom field ID.
location_idNoOptional GoHighLevel location ID override. Defaults to GHL_LOCATION_ID.
response_formatNoOutput format: markdown for human-readable summaries, json for structured output.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the agent knows it is a safe read operation. The description adds the endpoint path but does not expand beyond that. No contradiction exists, but no additional behavioral details (e.g., rate limits, authorization) are provided.

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 that includes the endpoint, which aids understanding. There is no redundant information, and every word serves a purpose.

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?

Given no output schema, the description does not explain the return format, but the tool name and context imply it returns the custom field data. Annotations provide safety guarantees. While it could mention output structure, the description is sufficiently complete for a simple retrieval tool.

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 schema already documents all three parameters. The description does not add any extra meaning beyond the schema; it merely restates the action. With high coverage, a score of 3 is 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?

The description clearly states the action ('get'), resource ('one custom field'), and context ('for a GoHighLevel location'). It includes the API endpoint, which adds specificity. This distinguishes it from sibling tools like list, create, update, delete, etc.

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

Usage Guidelines3/5

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

The description implies this is for retrieving a single custom field by ID, but it does not explicitly state when to use this versus alternatives like list (to get all fields) or search. No guidance on prerequisites or exclusions, relying on the tool name and sibling list for context.

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