GoHighLevel MCP

ghl_get_templates

Retrieve SMS, email, and WhatsApp quick-reply templates from your GoHighLevel location. Filter by template type to get specific templates.

Instructions

List SMS/email/WhatsApp templates in the location. These are the quick-reply-style templates under Settings → Templates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ghl_get_templates"
  }
}

Input Schema

Name	Required	Description
`skip`	No
`type`	No	Filter by template type
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It indicates a read-only list operation via 'List' and adds scoping to 'the location', but it does not mention pagination (skip/limit), return format, or any other behavioral traits such as whether the list is sorted. The description is honest but lacks deeper behavioral detail.

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?

The description is a single, well-structured sentence that front-loads the action ('List') and adds necessary context without wasted words. It is concise and easy to parse.

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 simple list tool with three optional parameters and no output schema, the description is largely complete: it names the resource, scope (location), and clarifies the specific subtype. It omits pagination details but the tool's simplicity keeps this from being a critical 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 only 33% (only 'type' has a description). The description adds no parameter information beyond naming the template channels, which somewhat reinforces the type enum. 'skip' and 'limit' remain undocumented in both schema and description, so the description fails to compensate for the low schema coverage.

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?

The description states 'List SMS/email/WhatsApp templates in the location' with a specific verb and resource. It further clarifies these are 'quick-reply-style templates under Settings → Templates', which distinguishes it from confusingly similar siblings like ghl_get_email_builder_templates.

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?

The description gives clear context ('quick-reply-style templates under Settings → Templates') that implies when to use this tool versus email builder templates, but it does not explicitly name alternatives or state exclusionary conditions. This is clear context without explicit when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server