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

ghl-mcp-server-v2

by zackscriven

ghl_chat_widget_delete

DestructiveIdempotent

Deletes a chat widget by its ID within a specific sub-account location, removing the widget from GoHighLevel via a DELETE request.

Instructions

Delete a Chat Widget Deletes a chat widget by ID Endpoint: DELETE /chat-widget/{locationId}/{id} (Version header: v3; source: v3/chat-widget-v3.json) Requires a Sub-Account (location) token. OAuth scopes: chat-widget.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": {
      "id": "<id>",
      "locationId": "<locationId>"
    },
    "name": "ghl_chat_widget_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe chat widget ID
locationIdYesThe location ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the OAuth scope chat-widget.write and the Sub-Account token requirement, which affects whether the call can succeed.

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

Conciseness4/5

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

Front-loaded with the action, then endpoint/auth metadata in compact lines. Every line carries information, though the title line and 'Deletes a chat widget by ID' are slightly redundant.

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 two-parameter destructive delete with no output schema, the definition covers action, endpoint, version, token type, and required scope. Annotations carry the irreversibility/idempotency signals, so an agent has what it needs; missing only explicit sibling/alternatives guidance.

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% and both parameters (id, locationId) are documented in the schema. The description confirms deletion is 'by ID' and shows locationId in the path template, but adds no format or constraint detail beyond the schema. Baseline 3 when the schema does the work.

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 a Chat Widget Deletes a chat widget by ID') and adds the exact endpoint. An agent can distinguish this from ghl_chat_widget_update/patch/clone without opening a schema.

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?

Implies when to use it (removing an existing widget by ID) and notes the Sub-Account token requirement, but gives no explicit exclusions or routing guidance versus siblings like ghl_chat_widget_update or ghl_chat_widget_patch.

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