Skip to main content
Glama

HighLevel Agency & Builder MCP

Save and check a site domain

ghl_domain_ssl_onboard
Destructive

Preview and save a domain record and funnel binding. Report DNS and HTTPS readiness separately. Hosting attachment, page routing and publication require separate steps.

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": {
      "domain": "<domain>",
      "funnelId": "<funnelId>"
    },
    "name": "ghl_domain_ssl_onboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
dryRunNo
stepIdNoOptional page ID to verify belongs to this funnel. This operation does not create or change its public route.
funnelIdYes
previewIdNo
locationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • removedInput schema / properties / domain / description
      Removed value: -"Custom funnel, website, or branded-link hostname."
    • addedInput schema / properties / domain / maxLength
      Added value: +512
    • addedInput schema / properties / domain / minLength
      Added value: +1
    • addedInput schema / properties / dryRun / default
      Added value: +true
    • removedInput schema / properties / dryRun / description
      Removed value: -"Verify DNS propagation and preview changes before applying."
    • addedInput schema / properties / funnelId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • 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 / previewId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / stepId
      Added value: +{
      +  "description": "Optional page ID to verify belongs to this funnel. This operation does not create or change its public route.",
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "domain",
      +  "funnelId"
      +]
  2. Changed11 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"Custom funnel, website, or branded-link hostname."
    • removedInput schema / properties / domain / maxLength
      Removed value: -512
    • removedInput schema / properties / domain / minLength
      Removed value: -1
    • removedInput schema / properties / dryRun / default
      Removed value: -true
    • addedInput schema / properties / dryRun / description
      Added value: +"Verify DNS propagation and preview changes before applying."
    • removedInput schema / properties / funnelId
      Removed value: -{
      -  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      -  "type": "string"
      -}
    • 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 / previewId
      Removed value: -{
      -  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      -  "type": "string"
      -}
    • removedInput schema / properties / stepId
      Removed value: -{
      -  "description": "Optional page ID to verify belongs to this funnel. This operation does not create or change its public route.",
      -  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "domain",
      -  "funnelId"
      -]New value: +[]
  3. Changed11 schema fields changed
    • removedInput schema / properties / domain / description
      Removed value: -"Custom funnel, website, or branded-link hostname."
    • addedInput schema / properties / domain / maxLength
      Added value: +512
    • addedInput schema / properties / domain / minLength
      Added value: +1
    • addedInput schema / properties / dryRun / default
      Added value: +true
    • removedInput schema / properties / dryRun / description
      Removed value: -"Verify DNS propagation and preview changes before applying."
    • addedInput schema / properties / funnelId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • 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 / previewId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / stepId
      Added value: +{
      +  "description": "Optional page ID to verify belongs to this funnel. This operation does not create or change its public route.",
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "domain",
      +  "funnelId"
      +]
  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, openWorldHint=true and non-idempotent, so the bar is lower. The description adds useful scoping ('requires separate steps') and notes DNS and HTTPS are reported separately, but it never warns that saving mutates the domain record, nor mentions that dryRun defaults to true or that the tool performs external DNS/HTTPS probes.

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 short sentences, front-loaded with the core action and followed by scope limits. No filler, though the second sentence ('Report DNS and HTTPS readiness separately') is slightly ambiguous about whether this tool performs the checks or just reports.

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 six-parameter, non-idempotent, destructive, open-world mutation with no output schema, the description omits too much: it does not explain the dry-run default, the roles of previewId/locationId, or what the agent should do with the DNS/HTTPS results. The multi-step caveat is helpful but insufficient.

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 only 17% of six parameters: only stepId is documented. The description never explains dryRun (the safety-critical preview switch), funnelId, previewId or locationId, so it fails to compensate for the coverage gap beyond the vague word 'Preview'.

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 uses specific verbs and resources: 'Preview and save a domain record and funnel binding.' It distinguishes the scope from siblings (e.g. ghl_site_builder_sync) by noting that hosting attachment, routing and publication are separate steps. It stops short of a fully crisp one-line statement of what 'save' means relative to the preview mode.

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?

It implicitly frames usage as verifying DNS/HTTPS readiness for a domain bound to a funnel, and explicitly excludes publishing/routing from this call. However, it never states when to choose this tool over the sibling sync/audit tools, nor when a preview-only pass is sufficient versus a real save.

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.