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

ghl-mcp-server-v2

by zackscriven

ghl_saas_update_rebilling

Bulk updates rebilling settings for multiple locations, including product, opt-in status, markup, and enabled state, using an agency-level token.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Update Rebilling Bulk update rebilling for given locationIds Endpoint: POST /saas/update-rebilling/{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_update_rebilling"
  }
}

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 / product / enum
      Previous value: -[
      -  "contentAI",
      -  "workflow_premium_actions",
      -  "workflow_ai",
      -  "conversationAI",
      -  "EmailNotification",
      -  "whatsApp",
      -  "reviewsAI",
      -  "VERIFIED_CALLER_ID",
      -  "WALLET_SALES_TAX",
      -  "NOTIFICATION_SMS",
      -  "EmailSmtp",
      -  "EmailVerification",
      -  "autoCompleteAddress",
      -  "funnelAI",
      -  "domainPurchase",
      -  "Phone",
      -  "Email"
      -]New value: +[
      +  "workflow_premium_actions",
      +  "EmailVerification",
      +  "contentAI",
      +  "workflow_ai",
      +  "whatsApp",
      +  "reviewsAI",
      +  "domainPurchase",
      +  "agentStudio",
      +  "askai",
      +  "aiStudio",
      +  "conversation_AI",
      +  "voiceAI",
      +  "Email",
      +  "Phone"
      +]
    • addedInput schema / properties / body / title
      Added value: +"UpdateRebillingDto"
  2. First observedv2.0.0

TDQS

A3.5/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 useful behavioral context not in annotations — the required agency/company-level token and the saas/company.write OAuth scope. It stops short of explaining whether the update overwrites existing rebilling config or is additive across the listed locations.

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 correctly front-loaded, but 'REQUIRES AN AGENCY-LEVEL (Company) TOKEN' is repeated verbatim later ('Requires an Agency (company-level) token'), and the version/source metadata line is spec provenance noise that does not help an agent decide or call.

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 endpoint are covered, which is the main risk for this tool, and no output schema exists so return values need not be described. Still missing is what the bulk operation actually does to locations already configured and whether partial failures are possible — meaningful gaps for a non-idempotent 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 coverage is 50%; the body's product, locationIds, and config fields are well documented in the schema itself. The description only indirectly clarifies companyId by showing it in the path template and tying it to an 'Agency (company-level) token', leaving its format and source unstated.

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 update rebilling'), the target scope ('for given locationIds'), and the exact endpoint POST /saas/update-rebilling/{companyId}. It does not explicitly name the closely-named sibling ghl_saas_update_rebilling_deprecated, so the agent must infer which one is current.

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 agency-token prerequisite is stated emphatically, which implicitly tells the agent this is not usable with a location-level token. However, there is no explicit guidance on when to choose this over ghl_saas_update_rebilling_deprecated, ghl_saas_allow_attach_rebilling, or ghl_marketplace_get_rebilling_config, and no note about failure modes for invalid locationIds.

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