ghl-gold

gold_ghl_workflow_bulk_enroll

Bulk enroll up to 25 contacts into a single GoHighLevel workflow via API, eliminating CSV imports for nurture blasts. Uses your GHL API key to loop the official add-to-workflow call.

Instructions

POWER: enroll up to 25 contacts into one workflow (loops the official add-to-workflow call). Nurture blast without CSV imports. BYOK GHL_API_KEY. PAID ONLY $39.

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": {
      "workflow_id": "<workflow_id>",
      "contact_ids": "<contact_ids>"
    },
    "name": "gold_ghl_workflow_bulk_enroll"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	must be CONFIRM to execute
`contact_ids`	Yes	max 25
`workflow_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 29, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the burden. It discloses that the tool loops the official add-to-workflow call, requires a BYOK GHL_API_KEY, and caps at 25 contacts. However, it does not disclose behavior around confirmation, idempotency, partial failures, or what happens if the workflow already contains a contact.

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

Conciseness3/5

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

The description is compact and readable, but includes extraneous marketing elements like 'POWER' and 'PAID ONLY $39' that do not help an agent invoke the tool. The core behavioral sentence is front-loaded, but the fluff weakens the overall structure.

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?

The description covers the core operation, the enrollment limit, the loop mechanism, and the auth requirement. However, for a write-like bulk operation with no annotations and no output schema, it omits important context such as confirmation handling, response format, error behavior, and whether enrollments are idempotent.

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

Parameters4/5

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

Schema coverage is 67%, and the description adds useful semantics: 'up to 25 contacts' clarifies contact_ids, 'enroll... into one workflow' clarifies workflow_id, and 'loops the official add-to-workflow call' explains how multiple contacts are processed. The confirm parameter is not addressed in the description, but the schema already documents its requirement.

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?

The description states a clear verb (enroll) with a specific resource (contacts into one workflow) and includes a concrete limit (up to 25) and mechanism (loops the official add-to-workflow call). This distinguishes it from siblings such as workflows_list, which is a list-only operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear context by framing the tool as a way to run nurture blasts without CSV imports, which implies a bulk-enrollment use case. It does not explicitly name alternatives or when-not-to-use conditions, but the intended scenario is reasonably clear.

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

Deploy Server