Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Find time trackings

find_time_trackings
Read-onlyIdempotent

The time-tracking transactions that are returned in this query include time tracking information that was entered into QuickBooks manually or gathered using the QuickBooks “Timer” or “Stopwatch.”

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, 3150 missing_element, 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, 3264 merchant_services_subscription_required

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_time_trackings"
  }
}

Input Schema

NameRequiredDescriptionDefault
txn_idNo`txn_id` is the unique QuickBooks identifier for a transaction. Use it to reference that transaction in later requests. Choose at most one of: `txn_id`, or the set (`max_returned`, `modified_date_range_filter`, `time_tracking_entity_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices.
iteratorNoPage through every match: QuBe Sync asks QuickBooks for each page in turn and sends each to your `webhook_url` as it arrives, all with the same `id`. On by default, with pages of 100 records; send `iterator=true` with `max_returned` for another size. Off when you send `iterator=false` (every match in one answer) or `max_returned` alone (at most that many, in one answer). It pages a filtered query only: with `txn_id` every match comes back in one answer, so leave `iterator` out.
meta_dataNoUse the `meta_data` attribute to control whether query responses include counts. Options are NoMetaData (default), MetaDataOnly (count only), and MetaDataAndResponseData (count plus objects).
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`.
max_returnedNoLimits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `meta_data` query attribute.) The page size, with `iterator=true`. Sent without `iterator`, or with `iterator=false`, it's a cap instead: at most this many records come back, in one answer, and QuickBooks doesn't say whether more matched. Choose at most one of: `txn_id`, or the set (`max_returned`, `modified_date_range_filter`, `time_tracking_entity_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
include_ret_elementNo
txn_date_range_filterNoFilters according to the original transaction dates. Choose at most one of: `txn_id`, or the set (`max_returned`, `modified_date_range_filter`, `time_tracking_entity_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices.
modified_date_range_filterNoFilters according to the dates when transactions were last modified. Choose at most one of: `txn_id`, or the set (`max_returned`, `modified_date_range_filter`, `time_tracking_entity_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices.
time_tracking_entity_filterNoAllows you to query for one or more names on the QuickBooks Vendor list, Employee list, or Other Names list. Choose at most one of: `txn_id`, or the set (`max_returned`, `modified_date_range_filter`, `time_tracking_entity_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices.

Output Schema

NameRequiredDescriptionDefault
urlYesReplace {connection_id} with the customer's connection.
qbxmlNoThe qbXML it compiles to. Only with include_qbxml.
queryYesThe query parameters: the arguments you passed.
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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, but the description adds genuinely non-obvious behavior: this compiles to a v2 request and the answer arrives asynchronously via a webhook payload, whose shape and status codes come back in response_json. It also enumerates twelve specific error codes (3260 insufficient_permission, 3250 feature_not_enabled, 3220 not_authorized, etc.), which tells the agent exactly what failure modes to handle — information no structured field carries. It stops short of describing page/webhook correlation beyond the schema's explanation.

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?

Two paragraphs plus a twelve-code error dump: the substantive content earns its place, but the first sentence is lifted verbatim from QuickBooks prose and reads as an incomplete clause, and the error list is a comma-run with no grouping. Front-loading is weak — the actual behavior (async webhook delivery) is buried at the start of paragraph two.

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?

With an output schema present and 90% schema coverage over ten parameters, the description need not restate return shape or filters, and it correctly spends its budget on the delivery mechanism and the error taxonomy. The remaining gap is that an agent gets no hint about prerequisites (QuickBooks Desktop connection, a configured webhook_url) or why this is read-only but asynchronous.

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 90%, so parameter meaning, mutual-exclusion rules, and the iterator/max_returned/page-size interaction are already fully documented in the schema. The description adds nothing about any of the ten parameters — no example query, no note on how txn_date_range_filter behaves for time trackings specifically.

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 opening sentence names the resource precisely — time-tracking transactions, including manually entered and Timer/Stopwatch-captured entries — so an agent knows the domain. But it is a noun-phrase fragment with no main verb (no 'find'/'query'), and it never distinguishes this from the nearby find_time_reports or create/update_time_tracking siblings. Clear resource identification, no sibling differentiation.

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 when-to-use, when-not-to-use, or alternative-selection guidance; the description never says to prefer this over find_time_reports or when a report query is the better call. The only routing logic (txn_id vs. the filter set, iterator vs. max_returned) lives in the schema, not the description. The scope sentence ('manually or via Timer/Stopwatch') describes what is included, not when to call it.

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