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

ghl-mcp-server-v2

by zackscriven

ghl_invoice_update_last_visited_at

Update an invoice's last-visited timestamp by invoice ID via PATCH /invoices/stats/last-visited-at, keeping invoice visit tracking current.

Instructions

Update invoice last visited at API to update invoice last visited at by invoice id Endpoint: PATCH /invoices/stats/last-visited-at (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": {
      "body": "<body>"
    },
    "name": "ghl_invoice_update_last_visited_at"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"PatchInvoiceStatsLastViewedDto"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write/non-destructive profile is covered. The description adds real value with the auth scope requirement and the versioned endpoint, but never explains what a "last visited at" update actually does server-side (e.g., whether the timestamp is set to now or supplied, and whether it affects stats only).

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?

Four short lines, front-loaded with the action, followed by auth and endpoint metadata. The API/source/version line is somewhat infrastructural but compact and not repetitive.

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?

For a one-parameter mutation with no output schema, the description covers the endpoint, version and auth scope, which is enough to invoke it. It leaves unclear what the resulting state or response is, so an agent cannot predict the effect of the call.

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% with a single documented invoiceId parameter, so the schema already carries the semantics and baseline 3 applies. The description's "by invoice id" merely restates the schema and adds no format or sourcing detail.

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?

The description states a specific verb and resource ("update invoice last visited at ... by invoice id") and names the endpoint, so an agent knows what the call mutates. It does not differentiate from the near-identical sibling ghl_estimate_update_last_visited_at, which a careful reader would want to distinguish.

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 guidance on when to use this tool, when not to, or how to choose it over the estimate counterpart or other invoice update tools. The only conditional statement is an auth prerequisite (Agency or Sub-Account token), which is a constraint rather than usage routing.

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