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

ghl-mcp-server-v2

by zackscriven

ghl_snapshot_create_share_link

Creates a share link for a GoHighLevel snapshot using an agency-level token, supporting permanent, agency, or location-restricted sharing.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only for all snapshots ops. Create Snapshot Share Link Create a share link for snapshot Endpoint: POST /snapshots/share/link (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>",
      "body": "<body>"
    },
    "name": "ghl_snapshot_create_share_link"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"CreateSnapshotShareLinkRequestDTO"
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds real value by disclosing the strict agency-level token requirement, which is a hard prerequisite not encoded in the schema or annotations. However, it does not say what the link looks like, whether links expire, or how share_type changes behavior.

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-loaded with the important auth constraint, but the agency-token requirement is stated twice (opening line and closing sentence), and the endpoint/version/spec-source metadata line is low-value clutter for an agent. Short overall but with redundant sentences.

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?

For a mutation tool with a nested request body and no output schema, the description covers auth and endpoint but says nothing about what is returned (presumably the share URL) or how each share_type behaves. It is adequate to attempt a call but leaves meaningful gaps around usage and results.

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 only 50%, with companyId undocumented in the schema; the description partly compensates by clarifying that the token/company is agency-level, implying companyId is the agency identifier. The nested body parameters (share_type, snapshot_id, share_location_id, relationship_number) are documented in the schema but not elaborated on in the description, so it adds only marginal meaning.

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: 'Create a share link for snapshot,' with the underlying endpoint POST /snapshots/share/link. It is clear what the tool does, though it does not distinguish itself from the other snapshot tools (list, get_latest_push, get_pushes_between_dates) in the sibling set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an auth prerequisite but no when-to-use guidance and no comparison against the other snapshot siblings. An agent knows it needs an agency token, but not when this tool is the right choice over listing or inspecting snapshots.

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