Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_email_template_create

Creates a new email template in a GoHighLevel sub-account, with fields for template name, editor type, sender, subject, and initial content.

Instructions

Create an email template Create a new email template Endpoint: POST /emails/locations/{locationId}/templates (Version header: v3; source: v3/emails-v3.json) Requires a Sub-Account (location) token. OAuth scopes: emails/templates.write

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": {
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_email_template_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"CreateTemplatePublicV2BodyDto"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the write/safety profile is covered. The description adds the endpoint and required token scope, but says nothing about behavior such as what happens on duplicate template names, whether the created template id is returned, or failure modes.

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?

Short and front-loaded, with the operation stated first. The opening two lines ('Create an email template' / 'Create a new email template') are redundant restatements, but the endpoint and scope lines carry genuine information, so waste is minimal.

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?

Adequate for a create tool whose parameters are fully documented and whose annotations cover safety: auth requirements and the endpoint are present. Missing pieces are the response (no output schema exists, so the description should say what a successful create returns, e.g. the new template id) and any cue distinguishing it from the email-builder template create sibling.

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% and the nested body properties (name, editorType, fromEmail, previewText, editorContent, parentFolderId) are fully documented in the schema itself. The description only reiterates locationId through the endpoint path, adding no meaning beyond structured data — the baseline 3 applies.

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 verb and resource (create an email template) plus the exact endpoint, so the operation is unambiguous. However, the description never distinguishes this from the nearby siblings ghl_email_builder_template_create, ghl_email_template_import, or ghl_email_template_update, leaving an agent to guess which create-variant to pick.

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 auth prerequisites (Sub-Account/location token, OAuth scope emails/templates.write) give real preconditions for calling it. Beyond that there is no when-to-use vs when-not guidance and no pointer to alternative template tools, so the routing decision is only implied.

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

Deploy Server

Other Tools