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

ghl-mcp-server-v2

by zackscriven

ghl_email_template_update

Updates an existing email template's name, subject line, sender details, content, preview text, or folder placement in GoHighLevel. Requires location and template IDs plus a request body with the fields to change.

Instructions

Update an email template Update email template Endpoint: PATCH /emails/locations/{locationId}/templates/{templateId} (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>",
      "templateId": "<templateId>",
      "body": "<body>"
    },
    "name": "ghl_email_template_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, openWorld=true, so the safety profile is largely covered. The description adds real context beyond that: the specific endpoint, version header, and auth requirements (Sub-Account token, OAuth scope). It does not disclose update semantics (partial vs replace, whether omitted fields are cleared) or the response shape, leaving meaningful gaps.

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 first two lines restate the same thing ("Update an email template" twice), which is pure redundancy. The endpoint, token, and scope lines are useful and reasonably front-loaded, but the duplicated lead wastes space.

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 mutation tool with rich schema and annotations, endpoint/auth/scope are covered, but there is no mention of the response (no output schema exists to compensate) or the effect of a partial vs full update. Adequate but with clear gaps an agent would want.

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 params already carry detailed descriptions including the conditional editorType/editorContent pairing and the null-to-root parentFolderId trick. The description contributes no parameter-level detail, so it sits at the baseline of 3 given the schema does the heavy lifting.

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 states a specific verb and resource ("Update an email template") and adds the concrete endpoint (PATCH /emails/locations/{locationId}/templates/{templateId}), so the agent knows exactly what resource is mutated. It does not differentiate from sibling update tools like ghl_email_builder_template_update or ghl_email_update_campaign, which keeps it from a 5.

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

Usage Guidelines2/5

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

No guidance on when to use this versus the many sibling template tools (create/delete/get/list, folder, import, builder template update). The only usage-adjacent statement is that a Sub-Account token and emails/templates.write scope are required, which is a prerequisite, not a when/when-not rule.

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