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

ghl-mcp-server-v2

by zackscriven

ghl_saas_bulk_disable

Bulk disables SaaS access for multiple locations using a company ID and location IDs; requires an agency-level token.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Disable SaaS for locations Disable SaaS for locations for given locationIds Endpoint: POST /saas/bulk-disable-saas/{companyId} (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": {
      "companyId": "<companyId>",
      "body": "<body>"
    },
    "name": "ghl_saas_bulk_disable"
  }
}

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: +"BulkDisableSaasDto"
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Goes meaningfully beyond annotations by disclosing the Agency/company-level token requirement, the OAuth scope saas/company.write, the HTTP endpoint and API version — all operational facts the annotations do not carry. It does not discuss reversibility (whether ghl_saas_bulk_enable restores state) or failure behavior, which keeps it below a 5.

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 agency-token requirement is front-loaded, which is good, but it is then repeated verbatim in the last line, and 'Disable SaaS for locations' appears twice in consecutive sentences. Redundancy costs space that could have carried the missing usage guidance.

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 two-parameter mutation with no output schema, the description supplies token level, auth scope, endpoint, and version — enough to attempt the call correctly. The remaining gap is that it says nothing about what the operation returns or whether disabling is reversible.

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 50%: locationIds is described in the schema and the description reinforces it, but companyId has no description anywhere — the agent must infer its meaning from the endpoint template. Baseline 3 is appropriate given partial schema coverage and no additional syntax guidance.

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 ('Disable SaaS for locations') plus the bulk scope via locationIds, which distinguishes it from the single-location sibling ghl_saas_enable_location. It does not, however, acknowledge ghl_saas_bulk_disable_deprecated, so an agent cannot tell from the text why this variant should be preferred.

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 text tells the agent the operation is bulk and agency-scoped, which implies when it applies, but never states when to prefer it over ghl_saas_bulk_disable_deprecated or over pausing versus disabling via ghl_saas_pause_location. No explicit exclusions or alternative routing.

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