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

ghl-mcp-server-v2

by zackscriven

ghl_email_builder_template_create

Create a new email builder template via the legacy Email Builder API, using a sub-account token and emails/builder.write scope.

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.] Create a new template Endpoint: POST /emails/builder (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_create"
  }
}

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

A4.3/5.0
Behavior5/5

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

Annotations already declare it is a non-idempotent, non-destructive write, but the description goes further: it discloses the Sub-Account (location) token requirement, the exact OAuth scope (emails/builder.write), the mandatory Version header, and deprecation status with a checked date. These are load-bearing operational details an agent cannot derive from the schema or annotations.

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?

Front-loaded with the highest-risk information (legacy/deprecated warning) before the endpoint metadata. Slightly repetitive—'Create a new template' restates the title and annotation title—but every remaining line carries operational value.

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 deprecated mutation tool with no output schema and a rich nested body, the description supplies the auth, versioning, and lifecycle context an agent needs to call it safely. It does not explain what the created template object looks like or any uniqueness/conflict behavior, a minor gap given no output schema exists.

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 documents all 11 properties with enums and examples, so the schema carries the parameter burden. The description adds no field-level guidance (e.g., how type interacts with importProvider/importURL), leaving it at the baseline for fully covered schemas.

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?

States a specific verb+resource ('Create a new template') and anchors it with the endpoint path, version header, and source spec. Crucially it distinguishes itself from the v3 template family by naming the different data model and warning they are 'not interchangeable', so an agent can separate it from siblings like ghl_email_template_create.

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?

Explicitly frames this as a legacy fallback with 'Expect removal; prefer a current equivalent', which tells the agent when not to use it. It stops short of naming the concrete alternative tool, so the agent must still infer which sibling replaces it.

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