GoHighLevel MCP

ghl_release_phone_number

Release a purchased phone number from your GoHighLevel location by passing its number ID. This deletes the number and frees it for other uses.

Instructions

Release (delete) a purchased phone number from the location.

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": {
      "numberId": "<numberId>"
    },
    "name": "ghl_release_phone_number"
  }
}

Input Schema

Name	Required	Description	Default
`numberId`	Yes	The phone number ID to release

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that the tool releases/deletes a phone number, but does not mention irreversibility, required permissions, or any side effects such as whether the number becomes available for repurchase. The description adds little beyond the tool name.

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, clear sentence that immediately states the action and scope. No redundancy or filler. It is concise and well-structured.

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 simple one-parameter destructive operation, the description is adequate but not complete. It does not specify what the tool returns (no output schema) or any prerequisites, such as the number being currently owned. It gives the essential action but lacks additional context that would be helpful for an agent.

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%, with the parameter already described as 'The phone number ID to release.' The description does not add any extra meaning or clarify the format or source of the ID, so it remains at baseline.

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 clearly states the action: 'Release (delete) a purchased phone number from the location.' It uses a specific verb and resource, and clarifies that 'release' means 'delete.' This distinguishes it from sibling tools like purchase, update, and get phone numbers.

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 purpose is clear, so when to use it is implied. However, there is no explicit guidance about alternatives or when not to use it. For instance, it doesn't mention whether updating the number to inactive is preferable in some cases. Usage is inferred from the action rather than stated.

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

Deploy Server