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

ghl-mcp-server-v2

by zackscriven

ghl_saas_enable_location

Enable SaaS for a GoHighLevel sub-account (location) by submitting the location ID and required SaaS configuration through an agency-level token.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Enable SaaS for Sub-Account (Formerly Location) Enable SaaS for Sub-Account (Formerly Location) based on the data provided

:::info This feature is only available on Agency Pro ($497) plan. ::: Endpoint: POST /saas/enable-saas/{locationId} (Version header: v3; source: v3/saas-api-v3.json) Requires an Agency (company-level) token. OAuth scopes: saas/company.write

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"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish that this is a non-readonly, non-idempotent, non-destructive, open-world operation. The description adds useful context beyond annotations: it requires an agency/company-level token, is limited to the Agency Pro plan, calls a specific endpoint, and needs the saas/company.write scope.

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?

The auth requirement is front-loaded well, but the title is repeated twice and the info block restates a prerequisite. The endpoint and scope information is useful, yet the description contains noticeable redundancy.

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 complex SaaS-enable mutation with a nested request body and no output schema, the description covers auth, plan restrictions, endpoint, and scopes. It still leaves gaps around parameter semantics, side effects of enabling SaaS, and expected response behavior.

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?

The description does not explain the required locationId or body parameters at all. Schema coverage is only 50%, and while many nested body fields have schema descriptions, the description does not compensate by clarifying required fields, V1 vs V2 requirements, or how to construct the request body.

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 and resource: 'Enable SaaS for Sub-Account (Formerly Location)'. This is clear enough to identify the operation, but it does not differentiate the tool from siblings such as ghl_saas_bulk_enable, ghl_saas_enable_location_deprecated, or ghl_saas_update_saas_subscription.

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 description gives important prerequisites: agency-level token, Agency Pro plan, and saas/company.write scope. However, it does not say when to use this tool instead of bulk enable, deprecated enable, or update subscription alternatives, so routing guidance is only implied.

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