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

ghl-mcp-server-v2

by zackscriven

ghl_phone_list_active_numbers

Read-onlyIdempotent

List active phone numbers for a specific location, with pagination, search filtering, and optional exclusion of number-pool numbers. Use it to inspect active numbers tied to a sub-account.

Instructions

List active numbers List active numbers. With version: v3, the HTTP 200 body is the standard success envelope (status, data, message, statusCode). The v3 list payload is under data; isUnderGhl is renamed to isUnderLc per AIP naming convention. Endpoint: GET /phone-system/numbers/location/{locationId} (Version header: v3; source: v3/phone-system-v3.json) Requires a Sub-Account (location) token. OAuth scopes: phonenumbers.read Pagination params: pageSize, page — pass them to page through full result sets.

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_active_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe page index. The default is 0.
pageSizeNoHow many resources to return in each list page. The default is 50, and the maximum is 1000.
locationIdYesLocation ID as string
searchFilterNoNumber search Filter
skipNumberPoolNoWhen true, exclude numbers assigned to number pools from the list.
includeRcsSenderIdsNoInclude RCS Sender IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful beyond-annotation context: the endpoint, version header, required Sub-Account token, OAuth scope, v3 success envelope, payload location under data, and the isUnderGhl-to-isUnderLc rename.

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?

Most sentences carry useful technical detail, but the description opens by repeating 'List active numbers' twice and then shifts into dense endpoint/auth metadata. It is appropriately sized overall, but the duplication and uneven structure reduce efficiency.

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?

With no output schema, the description supplies important context: endpoint, auth requirements, OAuth scope, response envelope, payload location, field rename, and pagination behavior. It still leaves the actual number object fields and filter semantics to the input schema, but it is largely complete for a read-only list operation.

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 itself documents all six parameters. The description adds pagination guidance for page and pageSize, but does not explain searchFilter, skipNumberPool, or includeRcsSenderIds beyond what the schema already says.

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 ('List active numbers') and gives the endpoint, so the basic purpose is clear. However, it does not distinguish this tool from siblings such as ghl_phone_list_available_numbers or ghl_phone_list_number_pools, and the opening sentence is duplicated.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no comparison to alternative phone-number listing tools. It mentions the required Sub-Account token and OAuth scope, but that is prerequisite information rather than selection 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