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

ghl-mcp-server-v2

by zackscriven

ghl_saas_allow_attach_rebilling

Marks a SaaS sub-account in setup_pending as awaiting rebilling attach, optionally stores product rebilling config, and sets payment_pending.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Allow Attach Rebilling Marks a SaaS sub-account as awaiting rebilling attach and optionally stores the rebilling configuration that should be applied when the rebilling config is created. Sets payment_pending on the sub-account. Only allowed when the sub-account is in setup_pending state. Endpoint: POST /saas/allow-attach-rebilling/{locationId} (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": {
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_saas_allow_attach_rebilling"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation ID (Sub-account) to allow attach rebilling for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / attachedRebillingConfig / additionalProperties / properties / enabled / description
      Previous value: -"Enable rebilling for the product"New value: +"Enable rebilling for this product"
    • changedInput schema / properties / body / properties / attachedRebillingConfig / additionalProperties / properties / markup / description
      Previous value: -"Additional value to be added in terms of percentage"New value: +"Markup multiplier applied on top of the base price, from 1 (1x) to 10 (10x). For domainPurchase the maximum is 3 (3x). Converted internally to a percentage markup (e.g. 2 -> 100%, 3 -> 200%)."
    • changedInput schema / properties / body / properties / attachedRebillingConfig / additionalProperties / properties / markup / example
      Previous value: -300New value: +3
    • changedInput schema / properties / body / properties / attachedRebillingConfig / additionalProperties / properties / price / description
      Previous value: -"Product price override"New value: +"Base price per unit (only applicable for usage based products like EmailVerification, agentStudio, contentAI)"
    • addedInput schema / properties / body / properties / attachedRebillingConfig / additionalProperties / title
      Added value: +"AttachedRebillingProductConfigDto"
    • addedInput schema / properties / body / title
      Added value: +"AllowAttachRebillingDto"
    • addedInput schema / properties / locationId / example
      Added value: +"AUKAtFVo0lWezBsBQ3FE"
  2. First observedv2.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond annotations, it discloses the agency-token requirement, the setup_pending precondition, and the important side effect of setting payment_pending on the sub-account. It also explains that the rebilling configuration is stored for later application when the rebilling config is created, which is significant behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and appropriately sized, with the token requirement and state precondition stated early. However, it repeats the agency-token requirement twice and includes a redundant title line, so not every sentence fully earns its place.

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?

Given the annotated mutation profile and fully documented nested schema, the description is largely complete: auth, endpoint, precondition, side effect, and optional config behavior are covered. It does not describe the response, which keeps it from a 5, but no output schema exists to define that for it.

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%, and the schema itself explains locationId and the nested body fields in detail. The description adds only high-level context about the optional stored configuration, so the schema remains the primary source for parameter semantics.

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?

The description states a specific verb and resource: it marks a SaaS sub-account as awaiting rebilling attach and optionally stores rebilling configuration. This is clearly distinct from sibling tools like update_rebilling or remove_attached_config because it identifies a particular setup-stage state transition and side effect.

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?

It gives strong when-to-use context by stating the sub-account must be in setup_pending state and that an agency-level token is required. It does not explicitly name alternatives or contrast with sibling rebilling tools, so it falls short of 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