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

ghl-mcp-server-v2

by zackscriven

ghl_saas_bulk_enable_deprecated

Bulk-enable SaaS mode for multiple locations using an agency-level token; deprecated, with the documented replacement preferred for new integrations.

Instructions

DEPRECATED per spec — superseded by POST /saas/bulk-enable-saas/{companyId}. 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.] Bulk Enable SaaS Enable SaaS mode for multiple locations with support for both SaaS v1 and v2 Endpoint: POST /saas-api/public-api/bulk-enable-saas/{companyId} (Version header: 2021-04-15; source: saas-api.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_saas_bulk_enable_deprecated"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description adds genuinely non-structured context: the agency/company-level token requirement and the lifecycle risk that the endpoint may be removed. It does not explain what actually changes on the locations or whether partial failures across multiple locationIds are possible, which matters for a multi-target mutation.

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 critical deprecation warning is correctly front-loaded, but it is restated three separate times in three bracketed forms, and the agency-token requirement appears twice. Cutting the redundant repeats would roughly halve the length with no loss.

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, nested-body mutation this covers the essentials an agent needs: auth scope, endpoint, version header, source, and removal risk, with no output schema to explain. The main remaining gap is the effect of enabling SaaS v1 vs v2 on the target locations.

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 every nested field (locationIds, isSaaSV2, saasPlanId, priceId, stripeAccountId) is documented in the schema itself. The description adds nothing beyond echoing companyId in the endpoint path, so the baseline 3 applies.

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 ('Bulk Enable SaaS — Enable SaaS mode for multiple locations with support for both SaaS v1 and v2') and flags itself as deprecated. It differentiates via the successor endpoint path rather than naming the sibling tool (ghl_saas_bulk_enable), so an agent must infer the mapping to the replacement.

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

Usage Guidelines4/5

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

Explicitly says to prefer the documented replacement and that this is a legacy fallback only still served under the old Version header. This is strong 'when-not-to-use' guidance, though it never states the positive condition under which calling this is the right choice.

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