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

ghl-mcp-server-v2

by zackscriven

ghl_email_template_list

Read-onlyIdempotent

Lists email templates for a GoHighLevel location, with pagination, search, folder filtering, and archive options so you can find and page through available templates.

Instructions

List templates Get list of templates by location Endpoint: GET /emails/locations/{locationId}/templates (Version header: v3; source: v3/emails-v3.json) Requires a Sub-Account (location) token. OAuth scopes: emails/templates.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_template_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of templates to return
offsetNoNumber of templates to skip
searchNoSearch by template name
sortByNoField to sort byupdatedAt
includeNoWhether to include templates, folders, or both in the response. `templates` will return only templates, `folders` will return only folders, and `all` will return both.all
archivedNoReturn archived templates
folderIdNoFolder to list templates from. Use 'root' for top-level listing.
sortOrderNoSort directiondesc
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description adds genuinely new context by stating the Sub-Account (location) token requirement and the required OAuth scope emails/templates.readonly. The pagination note adds behavioral detail about result-set traversal. It does not disclose the effective page-size cap or response shape, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then the endpoint, then auth and scope, then pagination — five short lines with no filler. Every line conveys distinct information an agent can act on.

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?

With no output schema, the description arguably should hint at the return contents, and it leaves out the 20-item page cap that materially affects how many calls a full listing requires. Still, endpoint, auth, scope and pagination are all supplied, which is close to complete for a read-only list tool.

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%, so all nine parameters are already documented in the schema; the baseline is 3. The description reinforces limit/offset as the paging mechanism and ties them to full result-set traversal, but adds nothing about the important maximum of 20 on limit or the semantics of include/folderId/archived.

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?

Names a specific verb+resource ('List templates') and pins it to an exact endpoint (GET /emails/locations/{locationId}/templates) with source spec. It does not differentiate from nearby siblings such as ghl_email_template_get, ghl_clientportal_list_templates, or ghl_email_builder_template_get, which an agent must disambiguate on its own.

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?

'Get list of templates by location' implies the retrieval context, and the pagination sentence tells the agent to page through results rather than stop at the first page. However there is no explicit when-to-use-vs-alternative guidance, no statement about when listing folders (include=folders) is preferable, and no exclusion of sibling template list tools.

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