Skip to main content
Glama

HighLevel Agency & Builder MCP

Build a workflow or call menu

ghl_workflow_ivr_builder
Destructive

Preview a form-screening, intake, or call-menu workflow, then apply that preview. For multi-step-intake, provide formId and input.tags (one to ten existing tag IDs), input.taskTitle and input.taskBody. Draft creation and publication are separate requested actions.

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": {
      "preset": "<preset>",
      "name": "<name>"
    },
    "name": "ghl_workflow_ivr_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
inputNo
phoneNo
digitsNo
dryRunNo
formIdNo
presetYes
publishNo
greetingNo
forwardToNo
previewIdNo
locationIdNo
workflowIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedInput schema / properties / digits
      Added value: +{
      +  "pattern": "^[0-9]{1,4}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / dryRun / default
      Added value: +true
    • removedInput schema / properties / dryRun / description
      Removed value: -"Preview workflow graph diff before publishing."
    • addedInput schema / properties / formId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / forwardTo
      Added value: +{
      +  "maxLength": 512,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / greeting
      Added value: +{
      +  "maxLength": 1000,
      +  "type": "string"
      +}
    • 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 / name
      Added value: +{
      +  "maxLength": 512,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / phone
      Added value: +{
      +  "maxLength": 512,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / properties / preset / description
      Removed value: -"Workflow or IVR blueprint preset to compile."
    • addedInput schema / properties / previewId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / publish
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / workflowId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "preset",
      +  "name"
      +]
  2. Changed16 schema fields changed
    • removedInput schema / properties / digits
      Removed value: -{
      -  "pattern": "^[0-9]{1,4}$",
      -  "type": "string"
      -}
    • removedInput schema / properties / dryRun / default
      Removed value: -true
    • addedInput schema / properties / dryRun / description
      Added value: +"Preview workflow graph diff before publishing."
    • removedInput schema / properties / formId
      Removed value: -{
      -  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      -  "type": "string"
      -}
    • removedInput schema / properties / forwardTo
      Removed value: -{
      -  "maxLength": 512,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • removedInput schema / properties / greeting
      Removed value: -{
      -  "maxLength": 1000,
      -  "type": "string"
      -}
    • 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 / name
      Removed value: -{
      -  "maxLength": 512,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • removedInput schema / properties / phone
      Removed value: -{
      -  "maxLength": 512,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • addedInput schema / properties / preset / description
      Added value: +"Workflow or IVR blueprint preset to compile."
    • removedInput schema / properties / previewId
      Removed value: -{
      -  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      -  "type": "string"
      -}
    • removedInput schema / properties / publish
      Removed value: -{
      -  "type": "boolean"
      -}
    • removedInput schema / properties / workflowId
      Removed value: -{
      -  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "preset",
      -  "name"
      -]New value: +[]
  3. Changed16 schema fields changed
    • addedInput schema / properties / digits
      Added value: +{
      +  "pattern": "^[0-9]{1,4}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / dryRun / default
      Added value: +true
    • removedInput schema / properties / dryRun / description
      Removed value: -"Preview workflow graph diff before publishing."
    • addedInput schema / properties / formId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / forwardTo
      Added value: +{
      +  "maxLength": 512,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / greeting
      Added value: +{
      +  "maxLength": 1000,
      +  "type": "string"
      +}
    • 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 / name
      Added value: +{
      +  "maxLength": 512,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / phone
      Added value: +{
      +  "maxLength": 512,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / properties / preset / description
      Removed value: -"Workflow or IVR blueprint preset to compile."
    • addedInput schema / properties / previewId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / publish
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / workflowId
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "preset",
      +  "name"
      +]
  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, non-idempotent and non-read-only, so the safety bar is lower. The description usefully adds the two-phase preview/apply model and that publication is a distinct action, but it never says what an apply overwrites or creates, whether existing workflows are touched, or what permissions are required.

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 with the two-phase nature front-loaded and no filler. The final sentence is slightly awkwardly phrased ('separate requested actions') but still earns its place by flagging draft vs publish.

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 13-parameter, destructive, nested-object tool with no output schema, the description is far from complete: it never explains how to move from preview to apply (previewId), what the nested input requires for the other two presets, or what a successful apply produces. It covers only a fraction of what an agent needs to invoke this safely.

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 13 parameters, including a nested 'input' object, so the description must carry the load. It only explains formId and three input.* fields for a single preset, leaving preset, name, phone, digits, dryRun, publish, greeting, forwardTo, previewId, locationId and workflowId entirely undocumented, and never relates dryRun to previewId.

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?

It states a specific verb pair (preview, then apply) and resource (form-screening, intake, or call-menu workflow) and names the three presets indirectly. The purpose is clear enough to distinguish it from the agency/ops siblings, which are unrelated, though 'apply that preview' stays abstract about what is actually created.

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 gives conditional guidance for one preset ('For multi-step-intake, provide formId and input.tags...') and clarifies that draft creation vs publication are separate requested actions. However, there is no guidance on when to pick which preset, when to publish vs only draft, or when to prefer dry-run, so usage remains implied rather than stated.

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.