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

ghl-mcp-server-v2

by zackscriven

ghl_location_get

Read-onlyIdempotent

Retrieve detailed information about a GoHighLevel Sub-Account (formerly Location) by passing its location ID, enabling account lookup and verification via the API.

Instructions

Get Sub-Account (Formerly Location) Get details of a Sub-Account (Formerly Location) by passing the sub-account id Endpoint: GET /locations/{locationId} (Version header: v3; source: v3/locations-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: locations.readonly

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

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuine context beyond that: the concrete endpoint, the v3 version header, and the required token type and OAuth scope (locations.readonly), which an agent needs to know before calling.

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?

Four short lines, front-loaded with the action and identifier, then endpoint and auth prerequisites. There is mild redundancy from repeating 'Sub-Account (Formerly Location)' in the title and body, but no wasted sentences.

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 with full annotation and schema coverage and no output schema, the description supplies endpoint, version, auth and scope, which is close to complete. It does not mention not-found behavior or what the returned record contains, a minor gap.

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% for the single parameter, so the schema already documents locationId. The description only restates that a sub-account id must be passed, adding no format or sourcing detail beyond the schema; baseline 3 applies.

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 (Get) and resource (Sub-Account/Location) plus the identifier needed to address it, which separates it from list/search-style siblings like ghl_location_search. It does not explicitly name an alternative or state what it returns, so it stops short of full sibling differentiation.

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 implied by 'by passing the sub-account id' and by the stated auth requirement (Agency or Sub-Account token), but there is no explicit when-to-use/when-not guidance versus ghl_location_search or ghl_company_get / ghl_business_get.

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