Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create payroll liability adjustment

create_payroll_liability_adjustment
Read-onlyIdempotent

Builds a v2 payroll_liability_adjustment.create request.

The payroll_liability_adjustment_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

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": {
      "is_affecting_accounts": "<is_affecting_accounts>",
      "payroll_liability_adjustment_line_add": "<payroll_liability_adjustment_line_add>"
    },
    "name": "create_payroll_liability_adjustment"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNo
txn_dateNo
class_refNo
def_macroNo
ref_numberNo
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`.
account_refNo
employee_refNo
payroll_dateNo
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
tax_table_versionNo
include_ret_elementNo
is_affecting_accountsYes
payroll_liability_adjustment_line_addYes

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

B3.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the tool compiles a request rather than executing it, that it returns both the v2 request and the webhook payload shape (response_json), and it enumerates the exact error codes/types to handle. This is meaningful context that annotations alone (readOnly/idempotent/destructive flags) do not convey, though the tension between a 'create' operation and readOnlyHint=true is never explicitly reconciled.

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 core purpose and return behavior are front-loaded in three tight sentences, which is good. The trailing multi-line dump of twenty-plus error codes is informative but verbose and reads like 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 return values need not be explained, and the error taxonomy is well covered. However, for a tool with 14 parameters, nested objects, and near-zero schema description coverage, the omission of any parameter semantics leaves a real gap for the calling agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14% across 14 parameters, and the description adds nothing about any of them — memo, txn_date, employee_ref, is_affecting_accounts, or the nested payroll_liability_adjustment_line_add fields. With the schema silent on nearly all inputs, the description should compensate but does not.

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 names a specific verb and resource ('Builds a v2 payroll_liability_adjustment.create request') and clarifies the dual input format (v2 body or the qbXML `payroll_liability_adjustment_add` wrapper). It is clear what the tool produces, but it never distinguishes itself from related siblings such as create_payroll_year_to_date_adjustment or find_payroll_liability_adjustments.

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 use this tool, when not to, or what the alternatives are. Preconditions such as the payroll subscription or posting-account requirements are only visible indirectly as raw error codes, not as instructions to the caller.

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