Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create transfer

create_transfer
Read-onlyIdempotent

Builds a v2 transfer.create request.

The transfer_add 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, 3175 in_use, 3176 locked, 3180 cannot_save, 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, 3270 missing_posting_account

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": "create_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNoAdditional information.
amountNoA monetary amount.
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.
def_macroNo`def_macro` lets you assign a reusable name to a returned `txn_id` or TxnLineID so later requests can reference it with `useMacro`. This feature requires SDK 2.0+.
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
transfer_to_account_refNoAccount that money will be transferred to.
transfer_from_account_refNoAccount that money will be transferred from.

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 and idempotent, which would look contradictory for a tool named 'create_transfer'; the description resolves this by explaining the tool only compiles a request and returns it plus the webhook payload shape. It also enumerates the failure codes an agent must handle. It does not state authentication requirements or whether anything is persisted, keeping it short of a 5.

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?

Purpose and output shape are front-loaded, which is good, but the 17-entry error-code list occupies roughly half the text and is partly self-undercutting: the text itself says 'the call result explains each,' so the list adds bulk without decision-relevant detail. Trimming to the few actionable codes would strengthen it.

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 10-parameter tool with nested reference objects, an output schema, and full annotation coverage, the description covers purpose, the returned request/webhook contract, and error handling, which is enough to call it correctly. The main gap is the absence of guidance on what to do with the compiled request (endpoint, sequencing) beyond 'send'.

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 coverage is 90%, so the schema already carries nearly all parameter meaning, making 3 the baseline. The description adds only two hints — the qbXML `transfer_add` acceptance and the fact that the returned request is intended to be sent — with no additional per-parameter semantics or ordering requirements for transfer_from_account_ref / transfer_to_account_ref.

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?

States a specific action and resource: 'Builds a v2 transfer.create request,' which immediately clarifies this is a request-builder rather than a mutating call. It also notes the qbXML `transfer_add` form is accepted. It does not differentiate itself from siblings such as update_transfer or create_transfer_inventory, so it falls short of a 5.

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 implied by the two-part flow described (build the request, send it, receive the answer via webhook), but there is no explicit when-to-use guidance and no statement of when a different tool should be chosen instead. Mentioning that `transfer_add` is accepted is an accepted-input note, not usage guidance.

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