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

ghl-mcp-server-v2

by zackscriven

ghl_invoice_template_delete

DestructiveIdempotent

Delete an invoice template by template ID and location, removing it from a GoHighLevel account. Use it when a template is no longer needed.

Instructions

Delete template API to update an template by template id Endpoint: DELETE /invoices/template/{templateId} (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: invoices/template.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": {
      "templateId": "<templateId>",
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_invoice_template_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYeslocation Id / company Id based on altType
altTypeYesAlt Type
templateIdYesTemplate Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the lower bar applies, and the description still adds useful operational context: the exact HTTP verb/path, that an Agency or Sub-Account token is required, and that the invoices/template.write OAuth scope is needed. It does not say what happens to invoices referencing the template or whether deletion is reversible, 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?

Short and front-loaded with the purpose, but the 'API to update an template by template id' sentence is not just wasted space - it is actively wrong for a delete tool. Endpoint/auth metadata is compact and earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-required-param destructive tool with no output schema but full annotation coverage, the auth and endpoint details make it callable, but the contradictory 'update' wording leaves an agent uncertain about the operation's actual effect.

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 the schema already documents templateId, altId, and altType including the enum for altType. The description only echoes 'by template id' and adds no syntax or format detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first line and endpoint (DELETE /invoices/template/{templateId}) make clear this deletes an invoice template, and the name places it among invoice_template_* siblings. But the second line reads 'API to update an template by template id', which directly contradicts the delete purpose and creates real doubt about what the tool does. Specific but internally inconsistent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this versus ghl_invoice_template_update, get, or list, and no warnings about when deletion is inappropriate. The only context given is prerequisites (token type, scopes), which is not usage guidance.

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