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

ghl-mcp-server-v2

by zackscriven

ghl_phone_list_number_pools

Read-onlyIdempotent

Lists GoHighLevel phone number pools for a specified location ID, helping you retrieve pool details before assigning or managing phone numbers.

Instructions

Spec declares no Version header for this endpoint (verified against the official spec, not an extraction gap) — the tool omits it accordingly. List number pools Returns number pools for the location. Requires locationId as a query parameter. Endpoint: GET /phone-system/number-pools (Version header: v3; source: v3/phone-system-v3.json) Requires a Sub-Account (location) token. OAuth scopes: numberpools.read

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>"
    },
    "name": "ghl_phone_list_number_pools"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation ID to scope the number pool list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-redundant context: it requires a Sub-Account (location) token and the numberpools.read OAuth scope, plus the underlying endpoint. That auth/scope detail is exactly what an agent needs before calling. It stops short of describing pagination or result shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description opens with an internal spec-extraction note ('Spec declares no Version header... the tool omits it accordingly') that is noise for an agent and actively confusing, since a later parenthetical says 'Version header: v3'. The substantive content — list, scope, token, scope name — is buried after that preamble instead of front-loaded.

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 single-parameter read tool with annotations covering safety and no output schema, the description supplies the remaining essentials: auth type, OAuth scope, and the HTTP endpoint. Only the return shape and pagination behavior are unaddressed, which is minor here.

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?

There is a single required parameter with 100% schema description coverage ('Location ID to scope the number pool list'), so the schema already carries the semantics. The description only restates that locationId is a query parameter, adding nothing beyond the schema — baseline 3.

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?

The description states a specific verb and resource ('List number pools') and scopes it to a location, which is enough to separate it from ghl_phone_list_available_numbers and ghl_phone_list_active_numbers. It never names those siblings explicitly, so the differentiation is left to the resource noun alone.

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?

Usage is only implied: the reader infers this is the call for enumerating existing pools on a sub-account. There is no statement of when to prefer it over the other phone-number listing tools, no prerequisites beyond the token requirement, and no exclusions.

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