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

ghl-mcp-server-v2

by zackscriven

ghl_email_builder_template_update

Update a legacy Email Builder (2021-07-28) template's HTML, builder elements, and settings using a sub-account token.

Instructions

Legacy 'Email Builder' template API (2021-era, distinct from the v3 template family below — different data model, not interchangeable). [LEGACY FALLBACK — this endpoint is no longer in the live v3 docs (checked 2026-10-28) but is still served under the legacy Version header. Expect removal; prefer a current equivalent.] Update a template Endpoint: POST /emails/builder/data (Version header: 2021-07-28; source: emails.json) Requires a Sub-Account (location) token. OAuth scopes: emails/builder.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": {
      "body": "<body>"
    },
    "name": "ghl_email_builder_template_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag it as mutating and non-idempotent; the description adds important deprecated/legacy context, endpoint version header, and required OAuth scope. It doesn't explain update semantics (full replace vs merge), but the added deprecation and auth context are valuable.

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?

The legacy/deprecation warning is front-loaded and directly relevant to tool selection. Endpoint and scope metadata are included without excessive verbosity, though some lines are more reference detail than call guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with a nested request body, no output schema, and adequate annotations, the description supplies legacy status, auth requirements, endpoint, and scope. Missing only explicit update semantics (e.g., whether omitted fields are preserved), but the essential information for correct invocation is present.

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 coverage is 100%, so the nested body fields are documented in the schema. The description adds no parameter-level meaning beyond noting the body is carried verbatim from the OpenAPI spec; 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?

The description names a specific verb and resource ('Update a template') within the 'Legacy Email Builder template API' and clearly differentiates it from the v3 template family ('different data model, not interchangeable'). It does not explicitly name the sibling replacement (e.g., ghl_email_template_update), but the legacy scoping makes the intent unambiguous.

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 explicitly warns that this endpoint is no longer in live v3 docs, is expected to be removed, and advises preferring 'a current equivalent.' It also states the prerequisite of a Sub-Account (location) token. An exact sibling alternative is not named, keeping it from a 5.

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