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

ghl-mcp-server-v2

by zackscriven

ghl_snapshot_list

Read-onlyIdempotent

Retrieves all owned and imported GoHighLevel snapshots for a company using an agency-level token, helping you audit or select available configurations.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only for all snapshots ops. Get Snapshots Get a list of all own and imported Snapshots Endpoint: GET /snapshots/ (Version header: v3; source: v3/snapshots-v3.json) Requires an Agency (company-level) token.

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": {
      "companyId": "<companyId>"
    },
    "name": "ghl_snapshot_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesCompany 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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-annotation context: that all snapshot operations are Agency-Access-Only and require a company-level token, plus the exact endpoint and version header. It omits pagination/result-size behavior, keeping it from a 5.

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?

Front-loading the critical auth warning is good, but the same requirement appears twice ('REQUIRES AN AGENCY-LEVEL (Company) TOKEN' and 'Requires an Agency (company-level) token'), and endpoint/source-file metadata is low-value filler for the model.

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 one-parameter read-only list tool with full annotation and schema coverage and no output schema, the description supplies the decisive missing piece (agency-level auth) plus the endpoint. Return shape and pagination are the only notable omissions, and they are minor here.

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 single companyId parameter is already documented in the schema. The description adds only indirect meaning ('Agency (company-level) token'), implying companyId is an agency-level identifier, but gives no format or sourcing guidance. Baseline 3 applies when the schema does the work.

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?

The description states a specific verb+resource: 'Get a list of all own and imported Snapshots', which is clearly distinct from sibling snapshot tools (create_share_link, get_latest_push, get_pushes_between_dates). It doesn't explicitly name those alternatives, but the list/read scope 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 only usage guidance is the repeated auth prerequisite (agency-level token). It never says when to prefer this over ghl_snapshot_get_latest_push or get_pushes_between_dates, so the agent must infer from the name that 'list all' is the broad enumeration case.

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