Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_object_update_record

Idempotent

Update a custom or standard object record in GoHighLevel by providing the schema key, record ID, location ID, and field values in the request body.

Instructions

SPEC GAP: UpdateCustomObjectRecordDto is an empty object schema in v3/objects-v3.json — verified against the raw spec, not an extraction bug. The body property will accept arbitrary JSON; GHL's convention (per external docs linked from this op, not confirmed in this corpus) is a properties object keyed by the object's field keys. Update Record Update a Custom Object Record by Id. Supported Objects are business and custom objects. Documentation Link - https://doc.clickup.com/8631005/d/h/87cpx-277156/93bf0c2e23177b0/87cpx-376296 Endpoint: PUT /objects/{schemaKey}/records/{id} (Version header: v3; source: v3/objects-v3.json)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesid of the record to be updated. Available on the Record details page under the 3 dots or in the url
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
schemaKeyYesThe key of the Custom Object / Standard Object Schema. For custom objects, the key must include the “custom_objects.” prefix, while standard objects use their respective object keys. This information is available on the Custom Objects Details page under Settings.
locationIdYes
Behavior2/5

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

Annotations provide readOnlyHint=false, idempotentHint=true, destructiveHint=false, but the description does not clarify if the update is partial or full replacement, nor does it explain idempotency or other behavioral implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose with a technical 'SPEC GAP' note and a documentation link that are not immediately actionable. The core purpose is buried, making it less efficient.

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

Completeness2/5

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

For a tool with a complex nested parameter (body) and no output schema, the description does not adequately explain the body format, constraints, or response structure. The spec gap note is confusing rather than helpful.

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 coverage is 75%; the description adds value for the 'body' parameter via the spec gap note explaining the empty schema and expected properties format. However, other parameters like 'locationId' lack additional context.

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 explicitly states 'Update a Custom Object Record by Id' and lists supported objects (business and custom objects). This clearly distinguishes it from sibling tools like create, delete, or get.

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 mentions it updates records by ID and supports business/custom objects, but lacks explicit when-to-use, when-not-to-use, or prerequisites. No guidance on alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zackscriven/ghl-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server