Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Find company activities

find_company_activities
Read-onlyIdempotent

A CompanyActivityQueryRq request message returns last_restore_time (the time when the company file was last restored from a back up), and last_condense_time (the time the company file was last condensed). It returns the default date of 1970-01-01 (UTC) for these elements if a restore or condense hasn’t happened for this company file. (For example, 1970-01-01 will be represented as 1969-12-31T16:00:00-08:00 in a time zone that is eight hours behind UTC.)

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_company_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
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`.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
include_ret_elementNo

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.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavior beyond them: the call is asynchronous (it returns a v2 request to send, with the answer arriving in a webhook `response_json`), and it enumerates the nine error codes with their types. The default-1970-01-01 semantics and the timezone rendering example are genuinely useful disclosure not present in the schema or annotations.

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 opening is jargon-first rather than front-loading the plain purpose, and the long parenthetical timezone worked example plus the nine-code error dump consume space disproportionate to their decision value. The error list earns some of its place, but the whole reads as reference material rather than guidance.

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?

An output schema exists, so the heavy emphasis on return values and sentinel defaults is partly redundant, while what is actually missing — the async round-trip workflow (send request, then await webhook) and any sibling differentiation — is only implied. Error handling and value semantics are well covered for a tool of this complexity.

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 67% and the description says nothing about `request_id`, `include_qbxml`, or `include_ret_element` directly. It does implicitly cover the enum values by explaining what `last_restore_time` and `last_condense_time` mean, which is modest added meaning over the bare enum, but the debugging flag and request label are left to the schema.

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 does name the concrete resource and payload: it returns `last_restore_time` and `last_condense_time` for a company file, plus the v2 request and webhook shape. The verb is buried under qbXML jargon ("A CompanyActivityQueryRq request message returns..."), and nothing distinguishes it from the many sibling `find_*` tools, but an agent can still infer what data comes back.

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 call this versus alternatives, no prerequisites, and no exclusions. The only contextual hint is the sentinel-value note about 1970-01-01, which tells the agent how to read results rather than when to request them.

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