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

ghl-mcp-server-v2

by zackscriven

ghl_email_template_delete

DestructiveIdempotent

Deletes an email template by location ID and template ID, removing it from the specified GoHighLevel sub-account.

Instructions

Delete a template Endpoint: DELETE /emails/locations/{locationId}/templates/{templateId} (Version header: v3; source: v3/emails-v3.json) Requires a Sub-Account (location) token. OAuth scopes: emails/templates.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": {
      "locationId": "<locationId>",
      "templateId": "<templateId>"
    },
    "name": "ghl_email_template_delete"
  }
}

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 destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the OAuth scope emails/templates.write and the requirement for a location-level token. It stops short of saying whether deletion is permanent, what happens on a non-existent templateId, or whether references break.

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?

Very short and front-loaded with the action, followed by endpoint and auth metadata on separate lines. The source-file provenance note is minor filler, but nothing is redundant or buried.

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, fully-required delete with rich annotations and no output schema, this covers the essentials: action, endpoint, auth token type, and scope. What is missing is failure/permanence behavior, which matters for a destructive operation.

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 both parameters are already documented, establishing the baseline. The endpoint line does add meaning by showing how locationId and templateId compose the path (hierarchical, location-scoped), but there are no format or validation details beyond the examples in 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 ('Delete a template') and maps it to a concrete endpoint, DELETE /emails/locations/{locationId}/templates/{templateId}, so the agent knows it targets email templates scoped to a location. However, siblings such as ghl_email_builder_template_delete and ghl_estimate_template_delete exist and the description never says which template family this deletes, so differentiation is incomplete.

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?

Usage is implied by the verb (call it when a template should be removed), and the requirement for a Sub-Account token implies the calling context. There is no explicit statement of when not to use it, no mention of alternatives, and no guidance on how to handle a template referenced elsewhere.

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