Skip to main content
Glama

HighLevel Agency & Builder MCP

Inspect the connected sub-account

ghl_agency_locations
Read-onlyIdempotent

Read the location profile, timezone and configuration for the connected sub-account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ghl_agency_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / company
      Removed value: -{
      -  "description": "Optional HighLevel company ID.",
      -  "maxLength": 16384,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Target HighLevel agency context.",
      -  "enum": [
      -    "moosh-growth",
      -    "marketplace-sandbox"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / location / description
      Removed value: -"Target sub-account location ID or alias."
    • removedInput schema / properties / location / maxLength
      Removed value: -16384
    • removedInput schema / properties / location / minLength
      Removed value: -1
    • addedInput schema / properties / location / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
  2. Changed6 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
      +  "description": "Optional HighLevel company ID.",
      +  "maxLength": 16384,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Target HighLevel agency context.",
      +  "enum": [
      +    "moosh-growth",
      +    "marketplace-sandbox"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / location / description
      Added value: +"Target sub-account location ID or alias."
    • addedInput schema / properties / location / maxLength
      Added value: +16384
    • addedInput schema / properties / location / minLength
      Added value: +1
    • removedInput schema / properties / location / pattern
      Removed value: -"^[A-Za-z0-9_-]{1,128}$"
  3. Changed6 schema fields changed
    • removedInput schema / properties / company
      Removed value: -{
      -  "description": "Optional HighLevel company ID.",
      -  "maxLength": 16384,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Target HighLevel agency context.",
      -  "enum": [
      -    "moosh-growth",
      -    "marketplace-sandbox"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / location / description
      Removed value: -"Target sub-account location ID or alias."
    • removedInput schema / properties / location / maxLength
      Removed value: -16384
    • removedInput schema / properties / location / minLength
      Removed value: -1
    • addedInput schema / properties / location / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
  4. Changed2 schema fields changed
    • removedInput schema / properties / action
      Removed value: -{
      -  "description": "Location operation to run (list, get, set, ensure).",
      -  "enum": [
      -    "list",
      -    "get",
      -    "set",
      -    "ensure"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / yes
      Removed value: -{
      -  "description": "Confirm apply after reviewing dry-run diff.",
      -  "type": "boolean"
      -}
  5. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the scope (connected sub-account) and enumerates the fields inspected, but says nothing about the default location resolution or whether openWorld implies remote API rate limits.

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

Conciseness4/5

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

One sentence, front-loaded with the verb and the returned fields, with no filler. It is efficient but arguably too terse for the ambiguity it leaves around the location parameter.

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?

No output schema exists, and the description does list the categories of returned data (profile, timezone, configuration), which is helpful. However, with an undocumented optional parameter and no default behavior stated, an agent cannot fully predict what a call without arguments will return.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the single 'location' parameter is never mentioned in the description — not its meaning, format, or what happens when it is absent. The phrasing "the connected sub-account" even implies no argument is needed, leaving the optional parameter's purpose unexplained.

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 ("Read") and concrete resources (location profile, timezone, configuration) scoped to the connected sub-account. An agent can distinguish it from the sibling health/contexts tools, though the boundary with ghl_agency_contexts is not drawn explicitly.

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?

No statement of when to use this versus ghl_agency_contexts or ghl_agency_connection_health, and no guidance on the case where the optional location argument is omitted. The agent must infer that this is the default/baseline inspection call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.