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

ghl-mcp-server-v2

by zackscriven

ghl_saas_bulk_enable

Bulk enable SaaS mode for multiple locations using one agency-level request, with support for SaaS v1 and v2.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Bulk Enable SaaS Enable SaaS mode for multiple locations with support for both SaaS v1 and v2 Endpoint: POST /saas/bulk-enable-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_enable"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / actionPayload / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "priceId": {
      -        "description": "Price ID for the SaaS plan",
      -        "example": "price_1QDPY5FpU9DlKp7RQ8BXfywx",
      -        "type": "string"
      -      },
      -      "providerLocationId": {
      -        "description": "Provider location ID",
      -        "example": "r06mdj4OrrERzYDvsOdh",
      -        "type": "string"
      -      },
      -      "saasPlanId": {
      -        "description": "SaaS plan ID",
      -        "example": "66c4d36534f21f900dc2a265",
      -        "type": "string"
      -      },
      -      "stripeAccountId": {
      -        "description": "Stripe account ID",
      -        "example": "acct_1QDPY5FpU9DlKp7RQ8BXfywx",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "saasPlanId"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "priceId": {
      +        "description": "Price ID for the SaaS plan",
      +        "example": "price_1QDPY5FpU9DlKp7RQ8BXfywx",
      +        "type": "string"
      +      },
      +      "providerLocationId": {
      +        "description": "Provider location ID",
      +        "example": "r06mdj4OrrERzYDvsOdh",
      +        "type": "string"
      +      },
      +      "saasPlanId": {
      +        "description": "SaaS plan ID",
      +        "example": "66c4d36534f21f900dc2a265",
      +        "type": "string"
      +      },
      +      "stripeAccountId": {
      +        "description": "Stripe account ID",
      +        "example": "acct_1QDPY5FpU9DlKp7RQ8BXfywx",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "saasPlanId"
      +    ],
      +    "title": "BulkEnableSaasActionPayloadDto",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / title
      Added value: +"BulkEnableSaasRequestDto"
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-readonly, non-destructive, non-idempotent, open-world behavior; the description adds genuinely useful context the annotations lack — agency/company-level token requirement and the saas/company.write OAuth scope. It does not describe partial-failure or per-location result behavior, which matters for a bulk 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 agency-token requirement is stated twice (opening line and 'Requires an Agency (company-level) token.'), which is redundant. The endpoint, header, and scope lines are useful and front-loaded, but the repetition costs it.

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?

Auth and scope are covered, but for a bulk mutation with nested required payload and no output schema, the description lacks any statement of outcome, partial-success handling, or limits (e.g., max locationIds). Its schema narrative defers entirely to the OpenAPI spec.

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% and the body's nested fields are well-documented in the schema. The description only implicitly clarifies companyId by embedding it in the endpoint path as the agency/company identifier; it adds nothing about body semantics. Baseline 3 is appropriate.

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+resource+scope: 'Bulk Enable SaaS mode for multiple locations' with support for both SaaS v1 and v2, plus the concrete endpoint. The 'bulk'/'multiple locations' wording distinguishes it from the singular ghl_saas_enable_location sibling.

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?

Usage is only implied by the word 'bulk' and 'multiple locations'; there is no explicit statement of when to use this versus ghl_saas_enable_location or the deprecated variant, nor any preconditions beyond the token requirement.

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