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

ghl-mcp-server-v2

by zackscriven

ghl_email_template_get

Read-onlyIdempotent

Retrieve a single email template by location ID and template ID to inspect its content and configuration for a GoHighLevel sub-account.

Instructions

Get Email Template by ID Get a single email template by its ID Endpoint: GET /emails/locations/{locationId}/templates/{templateId} (Version header: v3; source: v3/emails-v3.json) Requires a Sub-Account (location) token. OAuth scopes: emails/templates.readonly

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

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation ID
templateIdYesTemplate ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds genuinely new operational context: the exact REST path, the required v3 version header, that a Sub-Account (location) token is mandatory, and the emails/templates.readonly OAuth scope. Error behaviors and rate limits remain unstated.

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 purpose, followed by endpoint, auth, and scope metadata in a compact block. The first line and title are near-duplicates, which is the only waste.

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 two-parameter read operation with full annotation coverage, the description supplies what the annotations cannot: auth token type, required API version, and scope. The only gap is a hint at the returned template's shape, which is minor absent an output schema.

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% and both parameters carry descriptions, so the schema does the heavy lifting. The description's path template adds only that both are path parameters (location and template in the URL), not any format or validity semantics beyond the schema.

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 ('Get a single email template by its ID') and even the underlying endpoint, so the operation is unambiguous. It does not distinguish itself from lookalike siblings such as ghl_email_builder_template_get or ghl_location_get_all_or_email_sms_templates, which an agent would need to choose between.

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?

Use is implied by 'by its ID' — you fetch when you already hold a template ID — and the Sub-Account token prerequisite is spelled out. But no sibling is named as the alternative for listing/unknown-ID cases (ghl_email_template_list exists), so routing is left to inference.

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