@nightsquawktech/gohighlevel-mcp-server

Delete GoHighLevel Contact

ghl_delete_contact

Destructive

Delete a GoHighLevel contact by providing its contact ID. Requires explicit confirmation (confirm: true) to execute.

Instructions

Delete one GoHighLevel contact from /contacts/{contactId}. Requires confirm: true and owner approval before live execution.

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": {
      "contact_id": "<contact_id>",
      "confirm": "<confirm>"
    },
    "name": "ghl_delete_contact"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	Yes	Required for destructive tools. The API call is made only when confirm is explicitly true.
`contact_id`	Yes	Contact ID.
`response_format`	No	Output format: markdown for human-readable summaries, json for structured output.	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true, but the description adds value by revealing the requirement for explicit confirmation and owner approval before execution. This goes beyond the annotations and informs the agent of necessary preconditions.

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 sentence with no extraneous words. It front-loads the core action ('Delete one GoHighLevel contact') and efficiently adds constraints.

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 delete operation with three parameters and no output schema, the description covers the essential behavioral context (endpoint, required approval). It omits return value details, but that is not critical for a deletion tool. The information provided is sufficient for an agent to use the tool correctly.

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 coverage is 100% and parameter descriptions are thorough (e.g., confirm's role in destructive tools, contact_id's purpose). The description does not add additional semantic meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 explicitly states 'Delete one GoHighLevel contact from /contacts/{contactId}', specifying both the action (delete) and the resource (contact). It clearly distinguishes from read-only or creation sibling tools like ghl_get_contact or ghl_create_contact.

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?

The description implies usage context by requiring 'confirm: true and owner approval before live execution', which guides when to use the tool (when deletion is intended and authorized). However, it lacks explicit comparison to alternatives or when-not-to-use, such as pointing to ghl_search_contacts for finding contacts first.

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

Deploy Server