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

ghl-mcp-server-v2

by zackscriven

ghl_custom_field_update_folder

Idempotent

Update a custom field folder's name for GoHighLevel Custom Objects and Company records via the API.

Instructions

Update Custom Field Folder Name

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

Input Schema

NameRequiredDescriptionDefault
idYes
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare mutation (readOnlyHint=false), idempotency, and non-destructive behavior, so the bar is lower. The description does add real context beyond annotations: the exact endpoint, version header, required OAuth scope (locations/customFields.write), and the object-type limitation. It does not say that the existing folder name is replaced or how the body is applied.

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 first line is useful, but the raw HTML block adds nothing and injects the contradictory "Create Custom Field Folder" statement, wasting the most prominent position. The endpoint and OAuth lines are dense value, but the front-loading is wasted on noise.

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 simple mutation with annotations covering safety, no output schema, and a small nested body, the description covers endpoint, auth scope, and object-type limits. It still leaves the id/name semantics and the create-vs-update ambiguity unresolved, which is the main thing an agent needs.

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?

Schema coverage is only 50% and the description compensates for none of it: it never clarifies that `id` is the folder identifier (that property has no schema description) nor that `body.name` in the schema (mislabeled "Field name") is the new folder name. With a nested body object and a required locationId, this is a meaningful gap.

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 title and endpoint (PUT /custom-fields/folder/{id}) indicate renaming an existing custom field folder, but the embedded body text says "Create Custom Field Folder", which directly conflicts with the update semantics and leaves the agent second-guessing the verb. The specific resource (folder) and the object-type limitation are stated, so it is not a tautology, just muddled.

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?

Nothing says when to use this instead of the sibling ghl_custom_field_create_folder or ghl_custom_field_delete_folder. The note about only supporting Custom Objects and Company is a scope constraint, not usage guidance, and no prerequisites for the update are given.

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