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

ghl-mcp-server-v2

by zackscriven

ghl_invoice_template_list

Read-onlyIdempotent

Retrieves a paginated list of invoice templates for a location or company so you can browse and filter templates before selecting one.

Instructions

List templates API to get list of templates Endpoint: GET /invoices/template (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: invoices/template.readonly Pagination params: limit, offset — pass them to page through full result sets.

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>",
      "limit": "<limit>",
      "offset": "<offset>"
    },
    "name": "ghl_invoice_template_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYeslocation Id / company Id based on altType
endAtNoendAt in YYYY-MM-DD format
limitYesLimit the number of items to return
offsetYesNumber of items to skip
searchNoTo search for an invoice by id / name / email / phoneNo
statusNostatus to be filtered
altTypeYesAlt Type
startAtNostartAt in YYYY-MM-DD format
paymentModeNopayment mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior4/5

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

With readOnlyHint already declaring safety, the description still adds real context: it names the required token class (Agency or Sub-Account) and the OAuth scope invoices/template.readonly. It does not describe result shape or default page size, which keeps it short of a 5.

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 first two fragments are redundant with each other and with the title, wasting the front-loaded position. The endpoint, auth, scope and pagination lines are dense and useful, so the waste is limited but real.

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 9-parameter read-only list tool with no output schema, the description supplies auth requirements and paging guidance, which is the main thing schema fields cannot convey. Filter semantics are left to the schema, which is acceptable given full coverage.

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 100%, so the fields (altId, altType, search, status, startAt/endAt, paymentMode) are already documented. The description only adds that limit/offset should be used together to page through full result sets, which is a small increment over the schema.

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 description says "List templates" and "API to get list of templates," which largely restates the name. The endpoint path (GET /invoices/template) and the readonly scope hint that this is the invoice-template collection, but nothing distinguishes it from siblings like ghl_invoice_template_get or ghl_estimate_template_list.

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?

No guidance on when to use this versus ghl_invoice_template_get or ghl_estimate_template_list, nor prerequisites beyond token type. The only operational guidance is how to paginate, which is a mechanic rather than a when-to-use rule.

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