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

ghl-mcp-server-v2

by zackscriven

ghl_chat_widget_clone

Clone an existing chat widget into a new widget by providing the location ID and source widget ID, with an optional name for the copy.

Instructions

Clone a Chat Widget Clones an existing chat widget into a new widget Endpoint: POST /chat-widget/clone (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": {
      "body": "<body>"
    },
    "name": "ghl_chat_widget_clone"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / chatWidgetId / description
      Previous value: -"chat widget ID"New value: +"ID of the widget to clone. Cloning is rejected with a 422 when the source widget’s stored chatType is outside liveChat and emailChat — the restriction is evaluated against the persisted widget, not against this request body."
    • addedInput schema / properties / body / title
      Added value: +"CloneChatWidgetDTO"
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, openWorld=true, and the description does not contradict them. It adds genuinely useful context beyond annotations: the exact endpoint, the v3 version header, the requirement for a Sub-Account (location) token, and the chat-widget.write OAuth scope. It stops short of saying that each call produces a distinct new widget or what the response contains.

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 and scope in compact lines. Minor redundancy between the title line and the 'Clones an existing chat widget' sentence, but nothing wasteful.

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?

With no output schema, the description should say what comes back (presumably the new widget's ID), since that is what an agent needs to chain further calls. Auth, scope and endpoint are covered, but the return value and the practical consequence of non-idempotency are left unstated.

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%, so both body fields (locationId, chatWidgetId) are already documented, including the 422 rejection rule for unsupported chatType. The description adds nothing about parameters, so the baseline of 3 applies.

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 gives a specific verb and resource ('Clones an existing chat widget into a new widget'), making the duplicate-from-existing semantics clear. It does not, however, explicitly contrast with the nearby ghl_chat_widget_create sibling, which also produces a new widget, so an agent must infer the distinction.

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 only implied: cloning is the right choice when you want to duplicate an existing widget rather than construct one. There is no explicit 'use this instead of create when...' statement, no prerequisites beyond the token/scope note, and no exclusions.

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