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

ghl-mcp-server-v2

by zackscriven

ghl_saas_update_rebilling_deprecated

Bulk updates SaaS rebilling settings for specified location IDs using an agency-level token; use only as a legacy fallback because the endpoint is deprecated.

Instructions

DEPRECATED per spec — superseded by POST /saas/update-rebilling/{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.] Update Rebilling Bulk update rebilling for given locationIds Endpoint: POST /saas-api/public-api/update-rebilling/{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_update_rebilling_deprecated"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare this is a non-read-only, non-destructive, non-idempotent, open-world mutation. The description adds genuinely useful context beyond that: it requires an Agency (company-level) token and only works with the legacy Version: 2021-04-15 header. It does not describe what the response looks like or whether omitted config fields retain existing values.

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 deprecation warning is correctly front-loaded, but it is repeated four times in overlapping bracketed banners before the actual purpose statement, inflating the description. Trimming the redundant deprecation lines would make the useful content (token requirement, endpoint) far more scannable.

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 schema-rich mutation with annotations and no output schema, the description covers auth level, endpoint/version, deprecation, and scope. It does not clarify whether the update is partial or full-replace for the supplied locations, which is the only meaningful remaining gap.

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%, with the body, product enum, locationIds, and config sub-fields (including a markup example) all documented inline. The description only restates the locationIds scoping and adds no format or semantics beyond the schema, so the baseline of 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?

The description states a specific verb and resource ('Bulk update rebilling for given locationIds') and scopes it to a company. It also establishes the tool's status as deprecated and points to the replacement endpoint, which effectively distinguishes it from the live sibling ghl_saas_update_rebilling. It falls short of 5 only because it names the replacement by endpoint path rather than by sibling tool name.

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

Usage Guidelines5/5

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

Explicitly says the tool is DEPRECATED per spec and per official docs, that it is superseded by POST /saas/update-rebilling/{companyId}, that it is a legacy fallback served only under the old Version header, and that removal should be expected. The agent knows exactly when to prefer the alternative.

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