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

ghl-mcp-server-v2

by zackscriven

ghl_saas_bulk_disable_deprecated

Disables SaaS for multiple locations in bulk using location IDs and an agency-level token; deprecated in favor of the current bulk-disable endpoint.

Instructions

DEPRECATED per spec — superseded by POST /saas/bulk-disable-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.] Disable SaaS for locations Disable SaaS for locations for given locationIds Endpoint: POST /saas-api/public-api/bulk-disable-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_disable_deprecated"
  }
}

Input Schema

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

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?

Adds genuinely useful context beyond annotations: agency-level (Company) token requirement, the exact endpoint and Version header, the source spec, and an explicit deprecation/removal warning with a check date. Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false), so this extra operational context is the value-add. It does not contradict them.

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?

Three overlapping deprecation statements say essentially the same thing (DEPRECATED per spec, DEPRECATED per official docs, LEGACY FALLBACK), and the actual purpose appears fourth in the text. Substantial redundancy and poor front-loading for what is a two-parameter call.

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 legacy endpoint with two fully-described parameters, annotations, and no output schema, the description covers auth scope, endpoint/version, and deprecation risk. Nothing an agent needs in order to invoke it is missing, though it could state the return shape expectation for a bulk mutation.

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%, so both companyId and body.locationIds are already documented. The description adds only that the token/company context is agency-level, which clarifies which companyId to supply but not the ID format or location-ID sourcing. 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 concrete verb+resource+scope: 'Disable SaaS for locations for given locationIds', and the deprecation line names the superseding endpoint (POST /saas/bulk-disable-saas/{companyId}), which maps onto the sibling ghl_saas_bulk_disable. It stops short of naming that sibling tool directly, so differentiation relies on the agent inferring endpoint-to-tool equivalence.

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?

'prefer the documented replacement if one exists' and 'Expect removal; prefer a current equivalent' give explicit when-not-to-use guidance, plus the agency-token prerequisite. The guidance is conditional ('if one exists') rather than pointing at a concrete named alternative, which keeps it below a 5.

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