Skip to main content
Glama

HighLevel Agency & Builder MCP

Check staff permissions

ghl_user_role_governance
Read-onlyIdempotent

Compare staff assigned to the connected sub-account with a selected permission preset. This audit does not change roles.

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": {
      "preset": "<preset>"
    },
    "name": "ghl_user_role_governance"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYes
locationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / locationId / description
      Removed value: -"Target HighLevel sub-account location ID."
    • addedInput schema / properties / locationId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • removedInput schema / properties / preset / description
      Removed value: -"Least-privilege role preset to audit against."
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "preset"
      +]
  2. Changed4 schema fields changed
    • addedInput schema / properties / locationId / description
      Added value: +"Target HighLevel sub-account location ID."
    • removedInput schema / properties / locationId / pattern
      Removed value: -"^[A-Za-z0-9_-]{1,128}$"
    • addedInput schema / properties / preset / description
      Added value: +"Least-privilege role preset to audit against."
    • changedInput schema / required
      Previous value: -[
      -  "preset"
      -]New value: +[]
  3. Changed4 schema fields changed
    • removedInput schema / properties / locationId / description
      Removed value: -"Target HighLevel sub-account location ID."
    • addedInput schema / properties / locationId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • removedInput schema / properties / preset / description
      Removed value: -"Least-privilege role preset to audit against."
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "preset"
      +]
  4. Changed3 schema fields changed
    • removedInput schema / properties / action
      Removed value: -{
      -  "description": "Role governance action to perform.",
      -  "enum": [
      -    "audit",
      -    "assign",
      -    "offboard"
      -  ],
      -  "type": "string"
      -}
    • addedInput schema / properties / locationId
      Added value: +{
      +  "description": "Target HighLevel sub-account location ID.",
      +  "type": "string"
      +}
    • changedInput schema / properties / preset / description
      Previous value: -"Least-privilege role preset."New value: +"Least-privilege role preset to audit against."
  5. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so 'does not change roles' largely restates what is already structured. The description adds no auth requirements, no rate-limit or openWorld caveats despite openWorldHint=true, and does not say what the comparison produces. With annotations carrying the safety profile, this is adequate but thin.

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

Conciseness5/5

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

Two short sentences, zero waste, with the core action front-loaded and the non-mutation caveat immediately after. Nothing here could be trimmed without losing meaning.

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?

There is no output schema, so the description should say what a 'comparison' returns (a mismatch list? per-staff pass/fail?), and it does not. Combined with the unexplained enum semantics and unstated permission requirements for an admin-facing audit, the definition is usable but incomplete for an agent trying to interpret results.

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%, so the description carries the full burden for two parameters. It does hint that the comparison targets the 'connected sub-account' (implying locationId defaults there) and names 'a selected permission preset', but it never explains what the four enum values (va-support, sales-rep, client-admin, agency-admin) mean or what happens when locationId is supplied. That leaves real ambiguity an agent must guess through.

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: compare staff in the connected sub-account against a selected permission preset. The scope (sub-account staff, preset-based comparison) is clear enough to distinguish it from the agency-level siblings. It stops short of explicitly naming a sibling it is not, so a 4 rather than 5.

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 only guidance is the negative constraint 'This audit does not change roles,' which tells the agent what the tool is not for. There is no explicit statement of when to reach for this versus ghl_agency_contexts or ghl_custom_values_audit, nor any prerequisite such as requiring admin access. Usage is implied rather than specified.

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.