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

ghl-mcp-server-v2

by zackscriven

ghl_location_get_timezones

Read-onlyIdempotent

Retrieve the available timezones for a specified GoHighLevel sub-account location to support scheduling and localization.

Instructions

Fetch Timezones Fetch the available timezones Endpoint: GET /locations/{locationId}/timezones (Version header: v3; source: v3/locations-v3.json) Requires a Sub-Account (location) 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_timezones"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesPath parameter (inferred from the URL template; the official spec omits its declaration).

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?

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. Beyond those, the description usefully states the endpoint, version header, required Sub-Account token, and OAuth scope, which are relevant operational constraints. It does not describe response shape or pagination, but for a simple read-only GET that is a minor gap.

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?

The description is short and front-loads the core purpose, with endpoint and auth details following. The first two lines repeat essentially the same action, and the source-file metadata is less useful, but overall it remains efficient.

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 simple read-only endpoint with one required parameter, no output schema, and annotations covering safety, the description provides enough context to call the tool correctly. A note about the response format would improve completeness, but the core operation is clear.

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 single locationId parameter is already documented by the schema. The description only reinforces that locationId is part of the URL path and adds no further semantics such as format or examples.

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 uses a specific verb and resource: it fetches available timezones, and the endpoint path confirms it is scoped to a location. It does not explicitly differentiate this tool from any sibling, but the resource 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?

Usage is implied by 'Fetch the available timezones,' and the description adds required authentication context via the Sub-Account token and OAuth scope. It does not say when to use this tool versus alternatives or describe any 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