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

ghl-mcp-server-v2

by zackscriven

ghl_custom_menu_delete

DestructiveIdempotent

Delete a custom menu from GoHighLevel by its unique ID within a company. Requires an agency-level token and custom-menu-link.write scope.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only for all custom-menus ops. Delete Custom Menu Link Removes a specific custom menu from the system. This operation requires authentication and proper permissions. The custom menu is identified by its unique ID, and the operation is performed within the context of a specific company. Endpoint: DELETE /custom-menus/{customMenuId} (Version header: v3; source: v3/custom-menus-v3.json) Requires an Agency (company-level) token. OAuth scopes: custom-menu-link.write

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": {
      "customMenuId": "<customMenuId>"
    },
    "name": "ghl_custom_menu_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
customMenuIdYesID of the custom menu to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover destructive/readOnly/idempotent hints, so the description's added value is the auth disclosure: agency-level token requirement and the specific OAuth scope, which the agent otherwise cannot infer. It stops short of noting irreversibility or side effects on linked resources, keeping it below 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?

Front-loads the auth requirement, which is good, but then repeats it twice more ('Requires an Agency (company-level) token') and includes the redundant version-header/source metadata line. The deletion intent sentence is buried in the middle.

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?

For a single-parameter destructive delete with full annotation coverage, auth requirement and endpoint stated, the description gives an agent everything needed to call it. Only a note on irreversibility/side effects is missing.

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 100% with a single required customMenuId already documented in the schema. The description only restates that the menu is identified by its unique ID and that context is a specific company, adding no new format or constraint detail beyond the schema.

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?

States a specific verb+resource ('Delete Custom Menu Link', 'Removes a specific custom menu') and identifies the object by unique ID, plus names the exact endpoint DELETE /custom-menus/{customMenuId}. It is clearly distinguishable from sibling tools ghl_custom_menu_get_by_id, _update, _list and _create.

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?

Usage is implied by the delete verb, and the description adds a real precondition (agency/company-level token, OAuth scope custom-menu-link.write). However, it never states when to reach for this versus the sibling get/update tools, nor warns when deletion is inappropriate.

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