Skip to main content
Glama
Sign In
GoHighLevel MCP

GoHighLevel MCP

by NerdSnipe-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ghl_delete_custom_field

Delete a custom field from your GoHighLevel location by supplying its unique field ID. Remove unused or obsolete fields to clean up your workspace.

Instructions

Delete a custom field from the location.

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": {
      "fieldId": "<fieldId>"
    },
    "name": "ghl_delete_custom_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldIdYesCustom field ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states 'Delete', which inherently implies destruction, but does not disclose permanence, side effects, or any failure conditions. This is minimal information for a destructive operation.

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, front-loaded sentence with no redundant words. It is appropriately sized for such a simple tool.

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 tool's low complexity (one parameter, no output schema) and the clear purpose, the description is adequate for basic usage. However, the lack of behavioral details (e.g., permanence, error states) leaves room for improvement, especially without annotations.

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?

The single parameter is fully described in the schema ('Custom field ID to delete'), providing 100% coverage. The description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 uses the specific verb 'Delete' and clearly identifies the resource ('custom field') and scope ('from the location'). It is unambiguous and distinct from sibling tools by the action it performs.

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 usage is implied by the clear delete action, but there is no explicit guidance on when to use this tool versus alternatives like create/update/get custom fields, nor any mention of prerequisites or conditions.

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