Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Find companies

find_companies
Read-onlyIdempotent

A CompanyQueryRq request message returns detailed information about a QuickBooks company file, such as the company’s address and legal name, certain preferences that are set, and any services that the company is subscribed to, such as payroll, QuickBooks Merchant Services, and so forth. Company information can’t be added or modified through the SDK, only through the QuickBooks user interface. Note: If you include an explicit end tag in a CompanyQueryRq request, you will receive an error if there is any space between the opening tag and the end tag.

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

Input Schema

NameRequiredDescriptionDefault
owner_idNo`owner_id` identifies who owns the data extension. Use 0 for QuickBooks custom fields that appear in the UI, or use a GUID for private extensions owned by an app.
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

C2.9/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the bar is lower, and the description clears it with genuinely useful detail: the call returns a compiled v2 request and the agent must receive the answer asynchronously via a webhook payload, plus an enumerated set of error codes with types. It also flags a real operational quirk (an explicit end tag with leading whitespace causes an error). It stops short of saying whether requests are paginated or how the webhook is correlated beyond request_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structure is poor: the first sentence is a long run-on lifted from the QuickBooks SDK docs, the crucial 'returns the v2 request ... webhook payload' fact is buried mid-paragraph, and a note about whitespace inside XML tags is presented with equal prominence. The error-code list is useful but should be a trailing block; nothing is front-loaded.

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?

With an output schema and rich annotations present, the description doesn't need to explain return shapes, and it correctly covers the async request/webhook model and error surface. However, it leaves unclear how the returned data relates to the include_ret_element filter and what the caller must do after receiving the v2 request, which matters for a two-phase compile-then-receive flow.

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 75%, so the schema already documents owner_id, request_id, include_qbxml, and the include_ret_element enum. The description adds nothing parameter-specific — nothing about how include_ret_element narrows the response or what owner_id GUIDs mean in this context. Baseline 3 is appropriate when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that this surfaces company-file information (address, legal name, preferences, subscribed services) via a CompanyQueryRq, and late in the text reveals it returns a v2 request plus a webhook payload rather than the data itself. But that key framing is buried, and the opening is a pasted SDK paragraph that never names the tool's job in one clear verb+resource sentence. No differentiation from the many sibling find_* tools.

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 or when-not-to-use guidance, and no alternative tool is named despite dozens of sibling find_* tools. The statement that company info 'can’t be added or modified through the SDK' is a constraint on the domain, not routing guidance for an agent choosing between tools.

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