Skip to main content
Glama

HighLevel Agency & Builder MCP

Compare a sub-account with a snapshot export

ghl_snapshot_diff_audit
Read-onlyIdempotent

Compare a supplied snapshot export with this sub-account's live custom values, custom fields, tags and calendars. Include the snapshot ID and at least one asset category. The export is user-supplied; its ownership and freshness are unverified. Missing categories remain unverified. This does not overwrite assets.

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": {
      "snapshotId": "<snapshotId>",
      "snapshotExport": "<snapshotExport>"
    },
    "name": "ghl_snapshot_diff_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdNo
snapshotIdYes
snapshotExportYesSnapshot data containing id (or snapshotId), and arrays for customValues, customFields, tags or calendars, directly or under assets/resources. Use an empty array only for a category verified to be empty. Omit unavailable categories. Optional companyId must match the connected company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / locationId / description
      Removed value: -"Live HighLevel sub-account location ID to audit."
    • addedInput schema / properties / locationId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • addedInput schema / properties / snapshotExport
      Added value: +{
      +  "description": "Snapshot data containing id (or snapshotId), and arrays for customValues, customFields, tags or calendars, directly or under assets/resources. Use an empty array only for a category verified to be empty. Omit unavailable categories. Optional companyId must match the connected company.",
      +  "type": "object"
      +}
    • removedInput schema / properties / snapshotId / description
      Removed value: -"Reference Master Snapshot ID to compare against."
    • addedInput schema / properties / snapshotId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "snapshotId",
      +  "snapshotExport"
      +]
  2. Changed6 schema fields changed
    • addedInput schema / properties / locationId / description
      Added value: +"Live HighLevel sub-account location ID to audit."
    • removedInput schema / properties / locationId / pattern
      Removed value: -"^[A-Za-z0-9_-]{1,128}$"
    • removedInput schema / properties / snapshotExport
      Removed value: -{
      -  "description": "Snapshot data containing id (or snapshotId), and arrays for customValues, customFields, tags or calendars, directly or under assets/resources. Use an empty array only for a category verified to be empty. Omit unavailable categories. Optional companyId must match the connected company.",
      -  "type": "object"
      -}
    • addedInput schema / properties / snapshotId / description
      Added value: +"Reference Master Snapshot ID to compare against."
    • removedInput schema / properties / snapshotId / pattern
      Removed value: -"^[A-Za-z0-9_-]{1,128}$"
    • changedInput schema / required
      Previous value: -[
      -  "snapshotId",
      -  "snapshotExport"
      -]New value: +[]
  3. Changed6 schema fields changed
    • removedInput schema / properties / locationId / description
      Removed value: -"Live HighLevel sub-account location ID to audit."
    • addedInput schema / properties / locationId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • addedInput schema / properties / snapshotExport
      Added value: +{
      +  "description": "Snapshot data containing id (or snapshotId), and arrays for customValues, customFields, tags or calendars, directly or under assets/resources. Use an empty array only for a category verified to be empty. Omit unavailable categories. Optional companyId must match the connected company.",
      +  "type": "object"
      +}
    • removedInput schema / properties / snapshotId / description
      Removed value: -"Reference Master Snapshot ID to compare against."
    • addedInput schema / properties / snapshotId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "snapshotId",
      +  "snapshotExport"
      +]
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses real caveats: the export is user-supplied with unverified ownership and freshness, and missing categories stay unverified. 'This does not overwrite assets' largely restates destructiveHint=false, but the provenance warnings are substantive value the schema does not carry.

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?

Four short sentences, no filler, and the core comparison statement is front-loaded ahead of the caveats. The terse fragments ('Missing categories remain unverified') are dense with meaning rather than padding.

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?

A read-only audit tool with no output schema: the description never says what the diff returns (per-category difference lists? counts? verification status?), which is the main thing an agent needs to interpret results. Input-side caveats are well covered, so the gap is confined to output expectation.

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 only 33%, and the two 'non-obvious' items are undocumented: locationId has a pattern but no meaning in either place, while 'at least one asset category' refers loosely to arrays inside snapshotExport that only the nested schema spells out. The description does correctly reinforce snapshotId and the supplied-export nature of snapshotExport, but does not compensate for the locationId gap.

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 ('Compare') plus both operands (supplied snapshot export vs. live custom values, custom fields, tags, calendars), which is far more precise than the title alone. It never names the closest sibling, ghl_custom_values_audit, so an agent still has to infer why it would pick this over that one.

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?

'Include the snapshot ID and at least one asset category' sets a caller prerequisite, and 'This does not overwrite assets' implicitly signals a safe read-only use case. There is no explicit when-to-use/when-not guidance and no comparison against ghl_custom_values_audit or ghl_site_builder_sync, so selection among siblings remains inferred.

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.