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

ghl-mcp-server-v2

by zackscriven

ghl_invoice_template_update_payment_methods_configuration

Updates which payment methods are enabled for invoices created from a specific template, including Stripe bank-debit settings, by template ID.

Instructions

Updates which payment methods are enabled on invoices created from this template. Update template late fees configuration API to update template late fees configuration by template id Endpoint: PATCH /invoices/template/{templateId}/payment-methods-configuration (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account 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": {
      "templateId": "<templateId>",
      "body": "<body>"
    },
    "name": "ghl_invoice_template_update_payment_methods_configuration"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / paymentMethods / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "stripe": {
      -        "allOf": [
      -          {
      -            "properties": {
      -              "enableBankDebitOnly": {
      -                "description": "Enable Bank Debit Only",
      -                "example": false,
      -                "type": "boolean"
      -              }
      -            },
      -            "required": [
      -              "enableBankDebitOnly"
      -            ],
      -            "type": "object"
      -          }
      -        ],
      -        "description": "Payment Method"
      -      }
      -    },
      -    "required": [
      -      "stripe"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "stripe": {
      +        "allOf": [
      +          {
      +            "properties": {
      +              "enableBankDebitOnly": {
      +                "description": "Enable Bank Debit Only",
      +                "example": false,
      +                "type": "boolean"
      +              }
      +            },
      +            "required": [
      +              "enableBankDebitOnly"
      +            ],
      +            "title": "StripePaymentMethodDto",
      +            "type": "object"
      +          }
      +        ],
      +        "description": "Payment Method"
      +      }
      +    },
      +    "required": [
      +      "stripe"
      +    ],
      +    "title": "PaymentMethodDto",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / title
      Added value: +"UpdatePaymentMethodsConfigurationDto"
  2. First observedv2.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Useful additions exist: the HTTP method/path, API version header, source spec, and the Agency/Sub-Account token requirement. But the description then claims the endpoint updates late fees, directly conflicting with its own first sentence and with the actual path — a mutation tool that misstates what it mutates is a real hazard. It also omits whether changes are immediately effective on already-created invoices.

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

Conciseness2/5

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

The description is short but contains copy-paste residue: two sentences about late fees configuration that belong to a different tool, sandwiched between correct payment-method text. The redundant 'API to update...' line restates the preceding line, and the misleading content is front-loaded after the accurate sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-readonly, non-idempotent mutation with no output schema, the description should clearly state what is being changed and any side effects. It supplies auth scope and the endpoint, but the late-fees contamination means an agent cannot rely on it to know the tool's actual effect, and it says nothing about behavior for invoices already issued.

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 nested DTOs (altId, altType, paymentMethods.stripe.enableBankDebitOnly) are documented in the schema itself. The description adds only the templateId path placement; it does not explain the location/company altId relationship beyond what the schema says. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a concrete verb and resource: enabling/disabling payment methods on invoices generated from a template, which is reinforced by the PATCH endpoint. However, the middle two sentences say 'Update template late fees configuration,' which is a different resource (a sibling tool, ghl_invoice_template_update_late_fees_configuration, exists for exactly that). An agent reading the full description is left unsure whether this mutates payment methods or late fees.

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

Usage Guidelines2/5

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

There is no when-to-use/when-not-to-use guidance and no naming of alternatives, which matters here because the sibling late-fees tool and the general template-update tool overlap. The only precondition stated is 'Requires an Agency or Sub-Account token,' which is an auth requirement rather than routing guidance.

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