Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Update credit card credit

update_credit_card_credit
Read-onlyIdempotent

The Credit Card credit mod request allows you to modify an existing credit card credit transaction using the SDK. You can modify most of the fields that can be modified in the QuickBooks UI. That is, this request can be used to modify Purchased from, date, credit card and modify lines from the item table and the expense table.

The credit_card_credit_mod 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, 3170 cannot_modify, 3171 closing_date_modify, 3175 in_use, 3176 locked, 3200 stale_edit_sequence, 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

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": {
      "edit_sequence": "<edit_sequence>",
      "txn_id": "<txn_id>"
    },
    "name": "update_credit_card_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNoAdditional information.
txn_idYes`txn_id` is the unique QuickBooks identifier for a transaction. Use it to reference that transaction in later requests.
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.
ref_numberNo`ref_number` is a user-managed transaction reference (for example, a check number). It can be edited and is not guaranteed to be globally unique.
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`account_ref` points to an account in the company file. If both `full_name` and `list_id` are provided, `full_name` is ignored.
edit_sequenceYes`edit_sequence` is a server-generated revision token. It changes each time the object is updated. To modify an existing object, you must send the current `edit_sequence`.
exchange_rateNo`exchange_rate` is the rate from this currency to the company’s home currency at AsOfDate. You can supply a rate when adding transactions, but QuickBooks does not provide rates through the SDK.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
item_line_modNoAn ItemLine is used to track any portion of a transaction that represents the purchase of an “item.” `item_line_mod` and `item_group_line_mod` combine: any number of each. QuickBooks receives them in that order: every `item_line_mod`, then every `item_group_line_mod`.
is_tax_includedNoFor future use with international versions of QuickBooks.
clear_item_linesNoSet `clear_item_lines` to true to clear all the item lines. To modify individual lines, use `item_line_mod`.
expense_line_modNo
payee_entity_refNo`payee_entity_ref` identifies the payee (customer, vendor, employee, or Other Name). If both `full_name` and `list_id` are provided, `full_name` is ignored.
sales_tax_code_refNo`sales_tax_code_ref` points to the sales-tax code used for an item or customer context. QuickBooks includes default TAX and NON codes, and a code can be deleted only when nothing references it.
clear_expense_linesNoSet `clear_expense_lines` to true to clear all the expense lines. To modify individual lines, use `expense_line_mod`.
include_ret_elementNo
item_group_line_modNoRefers to items that are grouped together in QuickBooks for fast entry. `item_line_mod` and `item_group_line_mod` combine: any number of each. QuickBooks receives them in that order: every `item_line_mod`, then every `item_group_line_mod`.

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
Behavior1/5

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

The description explicitly presents a write operation ('modify an existing credit card credit transaction', 'used to modify Purchased from, date, credit card') while annotations declare readOnlyHint=true and destructiveHint=false. That is a direct contradiction an agent could act on incorrectly, so the otherwise-valuable error-code and webhook-payload detail cannot compensate.

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

Conciseness4/5

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

The opening paragraph is front-loaded and tells the agent what is modifiable before anything else. The 26-entry error-code list is dense but scannable and grouped by code, though the preamble ('The Credit Card credit mod request allows you to...') is wordier than needed.

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 an 18-parameter mutation with deep nesting and an output schema, the description covers the modifiable surface, the qbXML alias, the return/webhook shape, and the concrete failure modes — good coverage. It falls short only on concurrency semantics (`edit_sequence` requirement) and on the delete/clear semantics already hinted at by clear_item_lines and clear_expense_lines.

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 89%, so the schema already documents nearly every field, including the nested line modifiers and clear_* flags. The description adds only a high-level map of which fields are modifiable and does not explain the mod-vs-clear interaction, ordering of item/group lines, or the stale_edit_sequence workflow beyond the error code.

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 verb and resource ('modify an existing credit card credit transaction') and enumerates what can be changed: Purchased from (payee), date, credit card account, item lines and expense lines. The name and first sentence make the target object clear against create_credit_card_credit or update_credit_card_charge, though no sibling is named explicitly.

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?

Gives a useful scope statement ('modify most of the fields that can be modified in the QuickBooks UI') and notes that a `credit_card_credit_mod` qbXML wrapper is accepted, but never says when to prefer this over update_credit_card_charge or create_credit_card_credit, nor any prerequisite such as fetching a current `edit_sequence` before modifying.

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