Skip to main content
Glama

HighLevel Agency & Builder MCP

Check custom values and merge tags

ghl_custom_values_audit
Read-onlyIdempotent

Find blank custom values, unresolved placeholders, and broken references in the connected sub-account's message templates. Optional supplied templates are checked too.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ghl_custom_values_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
templatesNo
locationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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}$"
    • addedInput schema / properties / templates
      Added value: +{
      +  "items": {
      +    "maxLength": 20000,
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
  2. Changed3 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}$"
    • removedInput schema / properties / templates
      Removed value: -{
      -  "items": {
      -    "maxLength": 20000,
      -    "type": "string"
      -  },
      -  "maxItems": 50,
      -  "type": "array"
      -}
  3. Changed3 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}$"
    • addedInput schema / properties / templates
      Added value: +{
      +  "items": {
      +    "maxLength": 20000,
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
  4. Changed1 schema field changed
    • removedInput schema / properties / action
      Removed value: -{
      -  "description": "Validate templates for broken merge tags, diff values, or sync.",
      -  "enum": [
      -    "validate",
      -    "diff",
      -    "sync"
      -  ],
      -  "type": "string"
      -}
  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, idempotentHint, non-destructive and open-world, so the safety profile needs no restating. The description usefully adds scope: which account's templates are scanned and that supplied templates extend the scan. It says nothing about how 'broken references' are judged, severity, or report shape, which is fine to skip only because the annotations carry the risk profile.

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 sentences, no filler, with the primary scope stated first and the optional extension second. Every clause earns its place.

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?

Annotations cover the read-only/idempotent profile and the description covers scope, but with no output schema the agent has no picture of what an audit returns (counts, per-template findings, pass/fail) and no coverage of the locationId parameter. Adequate to invoke, thin for interpreting 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 must carry both parameters. It gives real semantics for `templates` (supplied templates get checked in addition to the sub-account's own), but `locationId` is never mentioned — the agent must infer it from 'connected sub-account', and nothing conveys the format constraint or that the array items are template strings.

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?

Specific verb ('Find') plus concrete defect classes (blank custom values, unresolved placeholders, broken references) scoped to message templates in the connected sub-account. An agent can tell this is a template-hygiene audit. It does not explicitly differentiate itself from adjacent audit tools like ghl_agency_doctor or ghl_snapshot_diff_audit.

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?

'Optional supplied templates are checked too' implies a default path (audit the sub-account) with an additive mode, so the intended usage is inferable. However, no condition is given for when to choose this over sibling audit/diagnostic tools, and no eligibility or prerequisite context is stated.

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.