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

ghl-mcp-server-v2

by zackscriven

ghl_invoice_schedule_update_and_activate

Updates a scheduled recurring invoice and activates its schedule using the provided schedule ID.

Instructions

Update scheduled recurring invoice API to update scheduled recurring invoice Endpoint: POST /invoices/schedule/{scheduleId}/updateAndSchedule (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: invoices/schedule.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": {
      "scheduleId": "<scheduleId>"
    },
    "name": "ghl_invoice_schedule_update_and_activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheduleIdYesSchedule Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.7/5.0
Behavior3/5

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

The description adds real context beyond annotations: the exact endpoint, the v3 version header, the Agency/Sub-Account token requirement, and the invoices/schedule.write OAuth scope. However, it never explains the mutation semantics — what state change occurs, whether an already-active schedule is affected, or that the call apparently also schedules/activates the invoice, which is the whole point of the name.

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 description is short and front-loads the purpose, but the second line ("API to update scheduled recurring invoice") is a pure restatement of the first with no added information. The endpoint/auth/scope metadata is compact and useful.

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-idempotent write tool with no output schema, the description leaves the critical question unanswered: what does this call change, and how does the 'activate' half differ from the plain update tool. Auth and endpoint details are present, but an agent could not confidently predict the effect of calling 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?

Only one parameter with 100% schema description coverage, so the baseline is 3. The description adds nothing about scheduleId (format, source, or lookup) beyond what the schema already shows, and notably does not reconcile the fact that an update operation exposes only an ID.

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?

"Update scheduled recurring invoice" restates the name/title, and the endpoint path (updateAndSchedule) hints at the activate step, but the description never explains what "update and activate" actually does beyond the update half. It also does not distinguish this tool from the close siblings ghl_invoice_schedule_update and ghl_invoice_schedule_activate, which an agent must be able to tell apart.

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 statement of when to choose this composite update-and-activate operation over plain ghl_invoice_schedule_update or ghl_invoice_schedule_activate. The only selection signal available is the tool name itself, so usage must be inferred.

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