Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Update time tracking

update_time_tracking
Read-onlyIdempotent

Modifies a time tracking transaction. This allows you to modify time entry and mark time entered as billed.

The time_tracking_mod wrapper from qbXML is also accepted. Returns the v2 request to send, and the webhook payload QuickBooks' answer arrives in (this operation's response_json: its data shape and the status codes to handle).

Possible errors (error.code / error.type; the call result explains each): 1030 unsupported_request, 3000 invalid_object_id, 3040 invalid_amount, 3070 string_too_long, 3120 object_not_found, 3140 invalid_reference, 3150 missing_element, 3170 cannot_modify, 3171 closing_date_modify, 3175 in_use, 3176 locked, 3200 stale_edit_sequence, 3210 invalid_value, 3220 not_authorized, 3231 request_not_processed, 3250 feature_not_enabled, 3260 insufficient_permission, 3261 personal_data_access_denied, 3262 payroll_subscription_required, 3263 read_only_access, 3264 merchant_services_subscription_required

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": {
      "duration": "<duration>",
      "edit_sequence": "<edit_sequence>",
      "entity_ref": "<entity_ref>",
      "txn_id": "<txn_id>"
    },
    "name": "update_time_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNo
notesNoAdditional information.
txn_idYes`txn_id` is the unique QuickBooks identifier for a transaction. Use it to reference that transaction in later requests.
durationYesTime spent doing the work. In a TimeTrackAdd request, notice that although you can specify seconds, seconds aren’t returned in the response because the UI doesn’t use seconds.
txn_dateNoThe date of the transaction. In some cases, if you leave `txn_date` out of an -Add message, QuickBooks will prefill `txn_date` with the date of the last-saved transaction of the same type.
class_refNoUse classes to categorize transactions (for example, by department, location, or work type). Class tracking is off by default in QuickBooks.
entity_refYesA QuickBooks “entity” is a customer, vendor, employee, or person on the QuickBooks “other names” list. Special cases to note: In a BillToPayQuery message, `entity_ref` refers to the vendor name.
request_idNoYour own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
customer_refNo`customer_ref` identifies a customer or customer job. If both `full_name` and `list_id` are provided, `full_name` is ignored. In SalesReceipt and ReceivePayment, it identifies who receives credit.
edit_sequenceYes`edit_sequence` is a server-generated revision token. It changes each time the object is updated. To modify an existing object, you must send the current `edit_sequence`.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
billable_statusNoThe billing status of this item line or expense line.
item_service_refNoA service item refers to services that a business charges for or purchases. Examples include specialized labor, consulting hours, and professional fees.
include_ret_elementNo
payroll_item_wage_refNoEach payroll wage item describes and names a payment scheme, for example, Regular Pay or Overtime Pay. A `payroll_item_wage_ref` aggregate refers to one of these wage items.

Output Schema

NameRequiredDescriptionDefault
urlYesReplace {connection_id} with the customer's connection.
bodyYesThe JSON body: the arguments you passed.
qbxmlNoThe qbXML it compiles to. Only with include_qbxml.
methodYes
headersYesSend with the request. Resent unchanged when no 201 came back, it answers with the request already queued.
webhookYesJSON Schema of the payload POSTed to webhook_url once QuickBooks answers, with this operation's response_json (data shape and status codes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is already covered. The description adds genuinely useful context beyond that: it explains the tool compiles and returns the v2 request plus the webhook payload shape the answer arrives in, and it enumerates the error codes the agent must handle. The leading "Modifies" wording is reconciled by the explicit "Returns the v2 request to send" sentence, which explains why the operation is read-only.

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 sentences are tight and front-loaded with purpose and capability. The third sentence is a dense parenthetical dump of roughly twenty error codes and the request/webhook mechanics, which is useful but unstructured and heavy relative to the rest.

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?

An output schema exists, so return-value shape need not be restated, and the description still explains the request/webhook delivery model and failure modes for this 15-parameter, nested-object mutation. What is missing is guidance on sequencing (retrieving edit_sequence before calling) and on the parameters the caller is most likely to get wrong.

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 high (87%), so the schema already documents the 15 parameters, including the edit_sequence concurrency token and billable_status. The description adds only indirect hints (billing status via "mark time entered as billed", qbXML wrapper acceptance) and does not explain required-field interplay or rate/duration semantics beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

"Modifies a time tracking transaction" gives a specific verb and resource, and the second sentence adds a concrete capability (mark time as billed). It does not name or distinguish itself from siblings such as create_time_tracking or find_time_trackings, so the agent gets a clear purpose but no disambiguation.

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 only implied: the agent must infer that this is the tool for changing an existing time entry rather than creating or locating one. There is no explicit when-to-use/when-not-to-use guidance and no statement of prerequisites (e.g., fetching the current edit_sequence first), even though the schema requires one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources