Skip to main content
Glama

HighLevel Agency & Builder MCP

Preview or apply a page change

ghl_site_builder_sync
Destructive

Read a funnel page or preview layout, style, copy, or content changes. Apply the returned preview to the same page. Existing checkout and upsell components must be preserved.

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": {
      "funnelId": "<funnelId>",
      "stepId": "<stepId>"
    },
    "name": "ghl_site_builder_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
inputNo
dryRunNo
stepIdYes
funnelIdYes
previewIdNo
locationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / dryRun / default
      Added value: +true
    • removedInput schema / properties / dryRun / description
      Removed value: -"Preview layout and CSS diff without mutating the live page."
    • removedInput schema / properties / funnelId / description
      Removed value: -"Target funnel or website ID."
    • addedInput schema / properties / funnelId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • addedInput schema / properties / input
      Added value: +{
      +  "type": "object"
      +}
    • removedInput schema / properties / locationId / description
      Removed value: -"Target HighLevel sub-account location ID."
    • addedInput schema / properties / locationId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • addedInput schema / properties / mode
      Added value: +{
      +  "enum": [
      +    "read",
      +    "draft",
      +    "styles",
      +    "copy",
      +    "content"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / previewId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • removedInput schema / properties / stepId / description
      Removed value: -"Optional funnel step or page ID."
    • addedInput schema / properties / stepId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "funnelId",
      +  "stepId"
      +]
  2. Changed12 schema fields changed
    • removedInput schema / properties / dryRun / default
      Removed value: -true
    • addedInput schema / properties / dryRun / description
      Added value: +"Preview layout and CSS diff without mutating the live page."
    • addedInput schema / properties / funnelId / description
      Added value: +"Target funnel or website ID."
    • removedInput schema / properties / funnelId / pattern
      Removed value: -"^[A-Za-z0-9_-]{1,128}$"
    • removedInput schema / properties / input
      Removed value: -{
      -  "type": "object"
      -}
    • addedInput schema / properties / locationId / description
      Added value: +"Target HighLevel sub-account location ID."
    • removedInput schema / properties / locationId / pattern
      Removed value: -"^[A-Za-z0-9_-]{1,128}$"
    • removedInput schema / properties / mode
      Removed value: -{
      -  "enum": [
      -    "read",
      -    "draft",
      -    "styles",
      -    "copy",
      -    "content"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / previewId
      Removed value: -{
      -  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      -  "type": "string"
      -}
    • addedInput schema / properties / stepId / description
      Added value: +"Optional funnel step or page ID."
    • removedInput schema / properties / stepId / pattern
      Removed value: -"^[A-Za-z0-9_-]{1,128}$"
    • changedInput schema / required
      Previous value: -[
      -  "funnelId",
      -  "stepId"
      -]New value: +[]
  3. Changed12 schema fields changed
    • addedInput schema / properties / dryRun / default
      Added value: +true
    • removedInput schema / properties / dryRun / description
      Removed value: -"Preview layout and CSS diff without mutating the live page."
    • removedInput schema / properties / funnelId / description
      Removed value: -"Target funnel or website ID."
    • addedInput schema / properties / funnelId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • addedInput schema / properties / input
      Added value: +{
      +  "type": "object"
      +}
    • removedInput schema / properties / locationId / description
      Removed value: -"Target HighLevel sub-account location ID."
    • addedInput schema / properties / locationId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • addedInput schema / properties / mode
      Added value: +{
      +  "enum": [
      +    "read",
      +    "draft",
      +    "styles",
      +    "copy",
      +    "content"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / previewId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • removedInput schema / properties / stepId / description
      Removed value: -"Optional funnel step or page ID."
    • addedInput schema / properties / stepId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "funnelId",
      +  "stepId"
      +]
  4. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, non-idempotent, open-world, so the safety profile is known. The description adds one genuinely valuable constraint ('existing checkout and upsell components must be preserved'), but does not say what applying a preview overwrites, how to escape dryRun, or that previewId binds the apply step.

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?

Three tight sentences with no filler, and the read/preview capability is front-loaded. The middle sentence is slightly ambiguous about whether 'the returned preview' refers to output of this same tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent, open-world tool with 7 undocumented parameters, a nested object, and no output schema, the description leaves far too much unspecified: no return shape, no mode semantics, no dryRun contract. Only the component-preservation rule is substantive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters including a nested free-form 'input' object, so the description must compensate and largely does not. It hints at the change categories that correspond to mode values, but never explains mode, dryRun (default true), previewId, locationId, or the funnelId/stepId pairing.

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?

States a specific two-phase operation: read/preview a funnel page for layout, style, copy, or content changes, then apply the returned preview to the same page. The verb+resource is clear, though the name 'sync' and the mode enum values are not reconciled with the described operations, and no sibling is split off.

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 sentence 'Apply the returned preview to the same page' implies a two-step read-then-apply workflow, which is useful. But there is no guidance on which mode value (read vs draft vs styles vs copy vs content) to pick, no mention that dryRun defaults to true, and no stated prerequisites or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.