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

ghl-mcp-server-v2

by zackscriven

ghl_custom_field_create_folder

Creates a custom field folder for GoHighLevel custom objects or Company records so related fields can be organized before creation.

Instructions

Create Custom Field Folder

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

Input Schema

NameRequiredDescriptionDefault
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: +"CreateFolder"
  2. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds context annotations do not carry: the required OAuth scope (locations/customFields.write) and the supported-object restriction. It stops short of disclosing duplicate-creation behavior implied by idempotentHint=false, which keeps it from a 5.

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

Conciseness3/5

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

The title 'Create Custom Field Folder' is repeated three times (name, plain text, and HTML paragraph) before any real information, which is wasted space. The actual value - the supported-object limitation - is front-loaded and clearly delineated, so the structure is serviceable but noisy.

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 single nested-object parameter tool with full schema coverage and no output schema, the description covers the essentials of what is created and where it is allowed. It does not indicate what is returned on success (folder ID, object shape) or how failures surface, which an agent would want given there is no output schema.

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% and each field (name, objectKey, locationId) is documented inline, so the baseline is 3. The description adds only marginal semantic value by tying objectKey to custom objects via the 'Only supports Custom Objects and Company' note; it gives no format or constraint details beyond the schema.

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 states a specific verb and resource (create a Custom Field Folder) and adds a meaningful scope constraint: only Custom Objects and Company (Business) are supported today. It does not explicitly differentiate from siblings such as ghl_custom_field_create, ghl_custom_field_update_folder, or ghl_custom_field_delete_folder, but the name and description together are unambiguous.

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 :::info block implies when this tool is applicable (custom objects and Company business objects only, other Standard Objects coming later), which is genuinely useful guidance. However, there is no explicit steering toward or away from sibling tools, no statement of prerequisites beyond the OAuth scope string, and no note on what to do if the folder already exists.

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