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

ghl-mcp-server-v2

by zackscriven

ghl_email_builder_template_delete

DestructiveIdempotent

Deletes a legacy Email Builder template using its location ID and template ID. Use it to remove an obsolete template from a specific Sub-Account.

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.] Delete a template Endpoint: DELETE /emails/builder/{locationId}/{templateId} (Version header: 2021-07-28; source: emails.json) Requires a Sub-Account (location) token.

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_builder_template_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYes
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/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 description isn't needed for the safety profile. It adds genuinely new context: deprecation risk ("Expect removal"), the required Sub-Account token scope, and the specific endpoint/version header used. It omits post-delete semantics (hard delete? error on unknown templateId?), 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.

Conciseness3/5

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

Dense and free of filler, but poorly front-loaded: the actual operation ("Delete a template") appears after two bracketed legacy/deprecation paragraphs, and the annotations' title repeats the same phrase. The metadata earns its place; its ordering does not.

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 only two required params, no output schema, and rich annotations, the definition supplies the remaining essentials: auth scope, version header, and the deprecation warning. Only the failure/return behavior of the delete is unaddressed.

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 0% for two required string params, but the description embeds the path template `DELETE /emails/builder/{locationId}/{templateId}`, which maps each argument to its role (sub-account location vs. template). It adds no format guidance (ID shape, error when the template belongs to another location), so it is adequate but not compensating fully for the 0% 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?

States a specific verb and resource ("Delete a template" for the legacy "Email Builder" template API) and explicitly distinguishes it from the v3 template family: "different data model, not interchangeable." An agent can separate this from ghl_email_template_delete without inspecting either schema.

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?

Gives clear routing context: legacy-only, served under the 2021-07-28 Version header, and "prefer a current equivalent." It stops short of naming the concrete alternative tool (ghl_email_template_delete) or stating the exact condition under which the legacy path is still required, so it is a 4 rather than a 5.

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