PineBill

Update estimate

update_estimate

Destructive

Update an existing estimate: status, lines, customer, dates, amounts, appearance and other fields. Find the estimate ID with list_estimates first, and resolve new customers or products with list_customers/list_products. Fields left out keep their current values. Passing items replaces every line with the given list, in that order. pdfUrl is a private, signed download link that expires at pdfUrlExpiresAt (1 hour). Give it to the user to open or download the PDF; don't put it in emails, notes, or anything that has to keep working.

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": {
      "id": "<id>"
    },
    "name": "update_estimate"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Estimate ID to update (from list_estimates)
`items`	No	The complete new list of lines, in print order. Replaces all current lines, so include the ones to keep.
`footer`	No	Footer printed at the bottom of every page. Plain text or simple HTML (p, br, h1-h3, strong, em, u, s, a, ul, ol, li, span with color or text-align); other markup and scripts are removed. An empty string means no footer.
`status`	No	New estimate status. When only status is given, the PDF is not regenerated.
`taxRate`	No	New tax rate
`taxType`	No	New tax type
`currency`	No	New currency code
`discount`	No	New discount as a fixed amount
`language`	No	Language of the printed labels and title. One of: en (English), de (German), fr (French), es (Spanish), pt (Portuguese), it (Italian), ar (Arabic), zh (Chinese), ja (Japanese), kr (Korean), tr (Turkish), az (Azerbaijani)
`template`	No	PDF design: regular (Regular), bold-professional (Bold Professional), tech-minimal (Mono), startup-modern (Startup Modern)
`issueDate`	No	New issue date (ISO string)
`projectId`	No	Project ID to link the estimate to, or null to unlink
`customerId`	No	New customer ID (replaces the current customer)
`dateFormat`	No	How dates print. 'Month DD, YYYY' prints December 31, 2025; 'Mon DD, YYYY' prints Dec 31, 2025; 'DD Mon YYYY' prints 31 Dec 2025
`endMessage`	No	New note to the customer printed after the totals (empty string clears)
`invoiceMode`	No	New estimate mode
`taxIncluded`	No	Whether tax is included in prices
`assignedToId`	No	Employee ID to assign the estimate to, or null to unassign
`customFields`	No	Replace all custom fields with these, in print order (empty array clears)
`invoiceTitle`	No	Document title printed at the top. Omit to keep the current title; an empty string resets it to the translated word for 'Estimate'.
`shippingCost`	No	New shipping cost
`currencyFormat`	No	How amounts print: NARROW_SYMBOL ($1,234.50), SYMBOL (US$1,234.50), CODE (USD 1,234.50), NAME (1,234.50 US dollars), ACCOUNTING (($1,234.50) for negatives)
`estimateNumber`	No	New estimate number
`termsOfPayment`	No	New terms (empty string clears)
`validUntilDate`	No	New expiry date (ISO string or null to clear)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the destructiveHint=true annotation: it declares partial-update semantics ('fields left out keep their current values'), the destructive replace-all behavior of items, and the conditional PDF regeneration rule when only status is supplied. It also discloses return-side behavior absent from any output schema — a private signed pdfUrl that expires after 1 hour and must not be persisted in emails or notes.

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-loads purpose and mutation semantics in the first three sentences, then the operational workflow, then the signed-link caveat. Dense but justified for a 25-parameter tool; the pdfUrl sentences are slightly tangential since pdfUrl is not an input parameter.

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 complex, highly destructive update with 25 parameters and no output schema, the description covers the non-obvious hazards (line replacement, partial updates, link expiry, regeneration condition). Minor gaps remain: it does not say how errors behave or whether the PDF regenerates for changes other than status-only.

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 schema already spells out replacement semantics for items and clearing behavior for fields, so the description earns baseline rather than credit for repetition. Its one genuine addition is the partial-update rule ('fields left out keep their current values'); the pdfUrl paragraph describes a return value, not a parameter, and could momentarily be mistaken for one.

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?

Opens with a specific verb+resource ('Update an existing estimate') and enumerates the field groups it can change (status, lines, customer, dates, amounts, appearance), so the agent knows the scope immediately. It does not explicitly distinguish itself from create_estimate/delete_estimate, but 'existing' plus the ID lookup makes the boundary clear in practice.

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

Usage Guidelines4/5

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

Gives concrete prerequisite workflow: look up the ID with list_estimates, and resolve customer/product references with list_customers/list_products before calling. It does not state when to choose this over create_estimate or delete_estimate, but for an update tool the usage context is effectively self-evident.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PineBill tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?