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

ghl-mcp-server-v2

by zackscriven

ghl_location_get_permissions

Read-onlyIdempotent

Retrieves permissions for a GoHighLevel sub-account location using an agency-level token, so you can verify access rights for a specific location.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only, despite the locations/write scope name. Get Permissions Get Sub-Account (Formerly Location) permissions Endpoint: GET /locations/{locationId}/permissions (Version header: v3; source: v3/locations-v3.json) Requires an Agency (company-level) token. OAuth scopes: locations/write

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

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Adds important non-obvious behavior beyond the annotations: the operation requires an Agency-level token despite the misleading `locations/write` scope name. It also identifies the exact GET endpoint and API version, though it does not describe the returned permission payload.

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?

The critical token warning is front-loaded, which is good. But the description repeats the token requirement and OAuth scope, and 'Get Permissions' appears redundantly, so not every line earns its place.

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 one-parameter read-only tool with rich annotations, the definition gives enough context to call it correctly: endpoint, version, auth requirement, and scope. Return-value details are absent, but the main invocation barriers are addressed.

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. The description adds only the endpoint path showing `{locationId}` and does not explain identifier format or source beyond the schema.

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: 'Get Permissions' for 'Sub-Account (Formerly Location) permissions', reinforced by the GET endpoint. It is clear but does not explicitly differentiate itself from the sibling ghl_location_update_permissions tool.

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?

Provides a meaningful prerequisite: an Agency (company-level) token is required. However, it does not explicitly say when to use this tool versus the sibling update_permissions tool, nor does it state exclusions or alternatives.

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