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

ghl-mcp-server-v2

by zackscriven

ghl_location_update_permissions

Idempotent

Update sub-account (location) permissions by specifying permission plans for a location ID.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Update Permissions Update Sub-Account (Formerly Location) permissions Endpoint: PUT /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>",
      "body": "<body>"
    },
    "name": "ghl_location_update_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"UpdatePermissionsDto"
  2. 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 cover the read/write and idempotency profile, and the description goes beyond them by disclosing the Agency-Access-Only security requirement and the exact OAuth scope — actionable context an agent cannot get elsewhere. It stops short of the one behavior that matters most here: whether the submitted permissions array replaces the location's entire permission set or is merged, which is left implicit against destructiveHint=false.

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 hard requirement is front-loaded ahead of everything else, and the body is short. Minor waste: the agency-token requirement is stated twice, and the OpenAPI source path (v3/locations-v3.json) is provenance metadata that does not help the calling agent.

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?

Only two required parameters, full schema coverage, and no output schema, and the description covers auth, scope, and endpoint. The remaining gap is behavioral: with destructiveHint=false and idempotentHint=true, an agent needs to know whether unlisted permissions are revoked, and the description is silent on that.

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 coverage is 100% and the enum of permission values is fully enumerated in the schema, so the description need not restate them. It does add value by mapping locationId to the path segment in PUT /locations/{locationId}/permissions, but says nothing about the semantics of the permissions array (full replacement vs additive), which is the key ambiguity.

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+resource ("Update ... Sub-Account (Formerly Location) permissions") and maps it to a concrete endpoint, so the agent knows exactly what changes. It does not name the read counterpart ghl_location_get_permissions or otherwise differentiate from siblings, but the verb+resource pair 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?

The prerequisite (agency/company-level token, locations/write scope) is stated explicitly, which is genuine usage guidance for an agent that may hold only a location token. However, there is no when-to-use vs when-not, no pointer to ghl_location_get_permissions for reading the current set first, and no guidance on when to prefer this over ghl_location_update.

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