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

ghl-mcp-server-v2

by zackscriven

ghl_email_builder_template_get

Read-onlyIdempotent

Fetch legacy Email Builder email templates for a specific location ID, with pagination, search, and archive filters. Use it to list or page through existing templates.

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.] Fetch email templates Fetch email templates by location id Endpoint: GET /emails/builder (Version header: 2021-07-28; source: emails.json) Requires a Sub-Account (location) token. OAuth scopes: emails/builder.readonly Pagination params: limit, offset — pass them to page through full result sets.

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>"
    },
    "name": "ghl_email_builder_template_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
limitNo
offsetNo
searchNo
archivedNo
originIdNo
parentIdNo
locationIdYes
sortByDateNodesc
templatesOnlyNo
builderVersionNo2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description layers on genuinely additional context: a 2021-era version header, a dated deprecation check, expected removal, the Sub-Account (location) token requirement, the emails/builder.readonly OAuth scope, and pagination behavior. These are operational facts an agent cannot get 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?

The deprecation warning is front-loaded in brackets and the endpoint/auth/scope/pagination lines are terse and scannable. Minor waste: 'Fetch email templates' is stated twice in consecutive lines, and the 'source: emails.json' metadata adds little for an agent.

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?

Auth, scope, deprecation risk, and pagination are well covered, and the annotations cover the safety profile, so an agent has enough to call the endpoint at all. But for an 11-parameter tool with 0% schema coverage and no output schema, leaving eight filter parameters completely undescribed is a real completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description only covers three of eleven parameters: locationId (by mention), limit, and offset. The remaining eight — name, search, archived, originId, parentId, sortByDate, templatesOnly, builderVersion — are never explained, and several have counter-intuitive string types (e.g. archived/limit typed as string with boolean/numeric defaults) that the description does nothing to clarify.

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 ('Fetch email templates') and scopes it to a location id, while explicitly setting this apart from the v3 template family with a different data model. It stops short of naming the actual sibling tool (e.g. ghl_email_template_list) that an agent should compare against, leaving the differentiation at the family level rather than the tool level.

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?

Strong guidance: the bracketed LEGACY FALLBACK block says this endpoint is no longer in live v3 docs, is still served under the legacy Version header, and to 'prefer a current equivalent' — a clear when-not-to-use signal. The gap is that it never names that equivalent tool, so the agent must guess among the many email template siblings.

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