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

ghl-mcp-server-v2

by zackscriven

ghl_invoice_generate_number

Read-onlyIdempotent

Retrieves the next invoice number for a specified location, ensuring sequential invoice numbering for GoHighLevel billing workflows.

Instructions

Generate Invoice Number Get the next invoice number for the given location Endpoint: GET /invoices/generate-invoice-number (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: invoices.readonly

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": {
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_invoice_generate_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id
altTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the description focuses on the additional context it alone can supply: the Agency/Sub-Account token requirement and the invoices.readonly OAuth scope. It does not address whether calling the endpoint consumes or reserves a number in the sequence, which matters given the idempotentHint=true annotation.

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?

Front-loaded with the operation and its effect, then endpoint and auth metadata in compact lines. Mild redundancy between the title line and "get the next invoice number", but nothing extraneous.

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 provenance are covered, but with no output schema the description never states what comes back (a bare number string, an object, whether it is a preview or a reserved number). For a number-generation tool the return contract is the main remaining unknown.

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%: altId is documented as "Location Id" but altType is only constrained by an enum. The phrase "for the given location" partially compensates by implying altType is always a location, but neither param gets format, example, or constraint detail beyond the schema.

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?

"Get the next invoice number for the given location" gives a specific verb and resource, clearly distinct from CRUD invoice siblings like ghl_invoice_create or ghl_invoice_get. It stops short of differentiating from the near-identical sibling ghl_estimate_generate_number, which an agent would have to infer from the name alone.

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 implied by "get the next invoice number for the given location" plus the stated token requirement, so the agent knows when it is callable. There is no explicit when-to-use/when-not guidance and no reference to the estimate-number sibling that could be confused with this one.

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