GoHighLevel MCP

ghl_create_email_campaign

Create a new email marketing campaign using an existing template. Set the subject line and schedule the send time.

Instructions

Create a new email marketing campaign (scheduled send) using an existing email builder template.

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": {
      "name": "<name>",
      "templateId": "<templateId>",
      "subject": "<subject>"
    },
    "name": "ghl_create_email_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Campaign display name
`subject`	Yes	Email subject line
`templateId`	Yes	Email builder template ID to use
`scheduledAt`	No	ISO 8601 datetime to schedule the send (e.g. 2025-06-01T10:00:00Z)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that this is a create/mutation operation and that it uses a template, but it does not mention return values, what happens if scheduledAt is omitted, or any side effects. This is a moderate level of transparency, sufficient for a straightforward create tool.

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

Conciseness5/5

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

The description is a single, concise sentence that front-loads the verb and key details. Every word adds value, and there is no redundancy or filler.

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?

For a simple create tool with no output schema and no annotations, the description covers the core purpose and the prerequisite (existing template). However, it lacks information about return values or error conditions, and the scheduling behavior is only implied by 'scheduled send'. Sibling tools are not referenced for disambiguation, leaving some gaps.

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 the baseline is 3. The description adds minimal parameter context beyond the schema: it clarifies that templateId refers to an existing email builder template. It does not elaborate on scheduledAt behavior or name/subject semantics, but the schema already describes these sufficiently.

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 clearly states the action (create), the resource (email marketing campaign), and a key differentiator (scheduled send using an existing template). This distinguishes it from siblings like ghl_send_email (immediate send) and ghl_create_email_builder_template (template creation).

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?

The description implies usage context: it creates a scheduled campaign and requires an existing template. While it doesn't explicitly list alternatives or exclusions, the phrase 'scheduled send' and 'using an existing email builder template' gives clear contextual guidance. Sibling tools like ghl_send_email are implicitly contrasted.

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

Deploy Server