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

ghl-mcp-server-v2

by zackscriven

ghl_saas_enable_location_deprecated

Enables SaaS for a GoHighLevel sub-account (location) using an agency-level token, as a deprecated legacy fallback; prefer the current POST /saas/enable-saas/{locationId} endpoint.

Instructions

DEPRECATED per spec — superseded by POST /saas/enable-saas/{locationId}. REQUIRES AN AGENCY-LEVEL (Company) TOKEN. [DEPRECATED per official docs — prefer the documented replacement if one exists.] [LEGACY FALLBACK — this endpoint is no longer in the live v3 docs (checked 2026-10-28) but is still served under the legacy Version header. Expect removal; prefer a current equivalent.] Enable SaaS for Sub-Account (Formerly Location)

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": {
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_saas_enable_location_deprecated"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation ID to enable SaaS for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond them: the required agency-level token scope, the plan gating (Agency Pro only), the Version header 2021-04-15, and the removal risk. It stops short of explaining what enabling SaaS actually provisions (subscription/rebilling side effects), which is the one behavioral gap for an irreversible mutation.

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

Conciseness2/5

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

Deprecation is correctly front-loaded, but the text contains three overlapping deprecation notices and states the agency-token requirement twice (top and bottom), plus an inline HTML warning block full of formatting markup. Roughly half the content is redundant or markup noise that does not earn its place.

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 deprecated, plan-gated mutation with a nested body and no output schema, the description covers replacement path, auth scope, plan restriction, and stability risk. It could be more complete by noting the irreversibility of enabling SaaS and what the response confirms, but nothing an agent needs to call it correctly is missing.

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 100% and the nested body fields (priceId, saasPlanId, isSaaSV2, stripeCustomerId, etc.) are already documented in the schema, so baseline 3 applies. The description itself only restates that locationId is the location to enable, adding no syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Enable SaaS for Sub-Account'), gives the exact endpoint POST /saas-api/public-api/enable-saas/{locationId}, and explicitly names the superseding endpoint, which maps to the non-deprecated sibling ghl_saas_enable_location. An agent can distinguish this from the current tool without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-not-to-use (DEPRECATED per spec and official docs, prefer the documented replacement), plus the fallback condition ('still served under the legacy Version header, expect removal'), plus hard prerequisites: Agency-level/Company token and Agency Pro ($497) plan. Nothing about selection is left to inference.

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