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

ghl-mcp-server-v2

by zackscriven

ghl_phone_purchase_number

Purchases a phone number for a specific location using payment and Twilio details, enabling number provisioning through the GoHighLevel phone system.

Instructions

Purchase number for location Purchase number for location. With version: v3, the HTTP 201 body is the standard success envelope (status, data, message, statusCode). The v3 purchase fields live under data: number, locationId, id, and underLcAccount (renamed from under_ghl_account). Endpoint: POST /phone-system/numbers/location/{locationId}/purchase (Version header: v3; source: v3/phone-system-v3.json) Requires a Sub-Account (location) token. OAuth scopes: phonenumbers.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>",
      "body": "<body>"
    },
    "name": "ghl_phone_purchase_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation ID as string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / numberType / description
      Previous value: -"type of phone number to be purchased"New value: +"Type of phone number to be purchased, e.g. 'local'. (Spec bug override 2026-08-27: upstream declares this as an empty object schema despite listing it in required[] — the tool was uncallable. The spec enumerates no valid values; pass a value you know from GHL docs, e.g. 'local'.)"
    • removedInput schema / properties / body / properties / numberType / example
      Removed value: -"local"
    • changedInput schema / properties / body / properties / numberType / type
      Previous value: -"object"New value: +"string"
    • addedInput schema / properties / body / title
      Added value: +"PurchasePhoneNumberBodyDto"
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, non-idempotent, open-world write, so the bar is lower, and the description adds real value on top: the auth token type, the required OAuth scope, and the exact v3 201 success envelope including the renamed underLcAccount field. It omits the commercial side of the operation (that purchasing incurs cost / requires a Stripe payment intent) and any error semantics, which keeps it from 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?

The opening sentence is literally duplicated and then a block of HTTP-endpoint and response-envelope detail is appended. Given there is no output schema the response detail earns its place, but the duplication and the spec-file provenance line (source: v3/phone-system-v3.json) are waste.

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 2-parameter, nested-body mutation with no output schema, the description covers the endpoint, version header, auth requirement, scope, and return payload fields — enough to call it correctly. Missing are billing/cost implications and the prerequisite that the number be available in the location's inventory.

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% and every body field (region, locality, addressSid, bundleSid, fingerprintId, etc.) is documented inline in the schema, so the schema carries the load. The description adds nothing about parameter meaning or ordering — the only body references describe returned fields, not inputs.

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 ("Purchase number for location") that is immediately distinguishable from the listing siblings (ghl_phone_list_available_numbers, ghl_phone_list_active_numbers). It does not explicitly name a sibling or explain how this relates to first discovering an available number, but the mutating intent is unambiguous.

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 supplies prerequisites (Sub-Account/location token, OAuth scope phonenumbers.write) which imply the calling context, but it never states when to use this versus the available-numbers listing tools or what to do if the purchase fails. Usage is inferable rather than guided.

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