conductor-node-mcp 12.36.1 → 12.38.0

package/README.md

@@ -226,6 +226,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_accounts` (`write`): Creates a new financial account. QuickBooks requires you to pick a supported account type for the chart of accounts, and non-posting types can’t be created through the API.
 - `retrieve_qbd_accounts` (`read`): Retrieves an account by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific accounts by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_accounts` (`write`): Updates an existing financial account. You can rename the account, adjust numbering, or change supported attributes, but QuickBooks won’t let you convert it to a non-posting type via the API.
 - `list_qbd_accounts` (`read`): Returns a list of accounts. NOTE: QuickBooks Desktop does not support pagination for accounts; hence, there is no `cursor` parameter. Users typically have few accounts.
 
@@ -233,6 +236,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_bill_check_payments` (`write`): Records a check payment against one vendor’s open bills. Each bill allocation must include a payment amount, discount, or vendor credit, and the accounts payable account has to match the one used on the bills you’re closing.
 - `retrieve_qbd_bill_check_payments` (`read`): Retrieves a bill check payment by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific bill check payments by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_bill_check_payments` (`write`): Updates a bill check payment so you can reallocate how amounts, discounts, or credits are applied to the vendor’s bills. When you update a payment, QuickBooks clears the prior allocations but keeps any existing vendor credits unchanged, so submit the full list of bill applications in this request.
 - `list_qbd_bill_check_payments` (`read`): Returns a list of bill check payments. Use the `cursor` parameter to paginate through the results.
 - `delete_qbd_bill_check_payments` (`write`): Permanently deletes a a bill check payment. The deletion will fail if the bill check payment is currently in use or has any linked transactions that are in use.
@@ -241,6 +247,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_bill_credit_card_payments` (`write`): Charges one vendor’s bills to a credit card account. Each bill allocation must supply a payment amount, discount, or credit, and you have to use the same accounts payable account that’s on the bills being closed.
 - `retrieve_qbd_bill_credit_card_payments` (`read`): Retrieves a bill credit card payment by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific bill credit card payments by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `list_qbd_bill_credit_card_payments` (`read`): Returns a list of bill credit card payments. Use the `cursor` parameter to paginate through the results.
 - `delete_qbd_bill_credit_card_payments` (`write`): Permanently deletes a a bill credit card payment. The deletion will fail if the bill credit card payment is currently in use or has any linked transactions that are in use.
 
@@ -249,6 +258,8 @@ The following tools are available in this MCP server.
 - `create_qbd_bills` (`write`): Creates a vendor bill and posts it to accounts payable. You can also link eligible purchase orders so QuickBooks pulls their lines onto the bill before it's saved.
 - `retrieve_qbd_bills` (`read`): Retrieves a bill by ID.
 
+  **IMPORTANT:** If you need to fetch multiple specific bills by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
   NOTE: The response automatically includes any linked transactions.
 
 - `update_qbd_bills` (`write`): Updates an existing vendor bill while keeping the required references intact. QuickBooks does not let this update request add new purchase order links, and you must continue to supply the vendor, accounts payable account, and at least one expense or item line when you resubmit the bill.
@@ -259,6 +270,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_build_assemblies` (`write`): Creates a build assembly transaction that consumes component quantities and increases the finished assembly on hand. If components are short you can mark the build as pending instead of failing.
 - `retrieve_qbd_build_assemblies` (`read`): Retrieves a build assembly by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific build assemblies by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_build_assemblies` (`write`): Updates an existing build assembly.
 - `list_qbd_build_assemblies` (`read`): Returns a list of build assemblies. Use the `cursor` parameter to paginate through the results.
 - `delete_qbd_build_assemblies` (`write`): Permanently deletes a a build assembly. The deletion will fail if the build assembly is currently in use or has any linked transactions that are in use.
@@ -268,6 +282,8 @@ The following tools are available in this MCP server.
 - `create_qbd_checks` (`write`): Creates a non-payroll check from a bank account. QuickBooks uses this request for direct expense disbursements; to pay vendor bills or payroll liabilities you must use the dedicated bill-payment or payroll transactions instead.
 - `retrieve_qbd_checks` (`read`): Retrieves a check by ID.
 
+  **IMPORTANT:** If you need to fetch multiple specific checks by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
   NOTE: The response automatically includes any linked transactions.
 
 - `update_qbd_checks` (`write`): Updates a standard check so you can adjust the issuing account, payee details, memo, transaction date, or expense and item lines. This request cannot modify checks created through the bill-payment workflow.
@@ -278,6 +294,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_classes` (`write`): Creates a new class.
 - `retrieve_qbd_classes` (`read`): Retrieves a class by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific classes by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_classes` (`write`): Updates an existing class.
 - `list_qbd_classes` (`read`): Returns a list of classes. NOTE: QuickBooks Desktop does not support pagination for classes; hence, there is no `cursor` parameter. Users typically have few classes.
 
@@ -289,6 +308,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_credit_card_charges` (`write`): Creates a new credit card charge for the specified account.
 - `retrieve_qbd_credit_card_charges` (`read`): Retrieves a credit card charge by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific credit card charges by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_credit_card_charges` (`write`): Updates an existing credit card charge so you can adjust the credit card account, payee, memo, transaction date, and expense or item lines. The total is recalculated from the line details.
 - `list_qbd_credit_card_charges` (`read`): Returns a list of credit card charges. Use the `cursor` parameter to paginate through the results.
 - `delete_qbd_credit_card_charges` (`write`): Permanently deletes a a credit card charge. The deletion will fail if the credit card charge is currently in use or has any linked transactions that are in use.
@@ -297,6 +319,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_credit_card_credits` (`write`): Creates a new credit card credit for the specified account.
 - `retrieve_qbd_credit_card_credits` (`read`): Retrieves a credit card credit by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific credit card credits by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_credit_card_credits` (`write`): Updates an existing credit card credit.
 - `list_qbd_credit_card_credits` (`read`): Returns a list of credit card credits. Use the `cursor` parameter to paginate through the results.
 - `delete_qbd_credit_card_credits` (`write`): Permanently deletes a a credit card credit. The deletion will fail if the credit card credit is currently in use or has any linked transactions that are in use.
@@ -305,6 +330,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_credit_card_refunds` (`write`): Creates a credit card refund linked to one or more existing credit transactions, such as credit memos or overpayments. You must supply at least one entry in `refundAppliedToTransactions`, and the refund amount cannot exceed the available balance on the linked credits.
 - `retrieve_qbd_credit_card_refunds` (`read`): Retrieves a credit card refund by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific credit card refunds by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `list_qbd_credit_card_refunds` (`read`): Returns a list of credit card refunds. Use the `cursor` parameter to paginate through the results.
 - `delete_qbd_credit_card_refunds` (`write`): Permanently deletes a a credit card refund. The deletion will fail if the credit card refund is currently in use or has any linked transactions that are in use.
 
@@ -313,6 +341,8 @@ The following tools are available in this MCP server.
 - `create_qbd_credit_memos` (`write`): Creates a new credit memo.
 - `retrieve_qbd_credit_memos` (`read`): Retrieves a credit memo by ID.
 
+  **IMPORTANT:** If you need to fetch multiple specific credit memos by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
   NOTE: The response automatically includes any linked transactions.
 
 - `update_qbd_credit_memos` (`write`): Updates an existing credit memo.
@@ -323,6 +353,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_currencies` (`write`): Creates a user-defined currency with the specified name and currency code. Exchange rates for user-defined currencies are not updated automatically by QuickBooks Desktop; update them manually as needed.
 - `retrieve_qbd_currencies` (`read`): Retrieves a currency by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific currencies by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_currencies` (`write`): Updates an existing currency. For built-in currencies, only the `isActive` status can be changed; name and currency code are not editable. For user-defined currencies, all fields in this request are editable.
 - `list_qbd_currencies` (`read`): Returns a list of currencies. NOTE: QuickBooks Desktop does not support pagination for currencies; hence, there is no `cursor` parameter. Users typically have few currencies.
 
@@ -330,6 +363,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_customers` (`write`): Creates a new customer.
 - `retrieve_qbd_customers` (`read`): Retrieves a customer by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific customers by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_customers` (`write`): Updates an existing customer.
 - `list_qbd_customers` (`read`): Returns a list of customers. Use the `cursor` parameter to paginate through the results.
 
@@ -337,6 +373,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_date_driven_terms` (`write`): Creates a date-driven term that sets the payment due on a specific day of the month and can optionally grant an early-payment discount before `discountDayOfMonth`. Use it when you need due dates tied to calendar days instead of a fixed number of days after the transaction.
 - `retrieve_qbd_date_driven_terms` (`read`): Retrieves a date-driven term by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific date-driven terms by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `list_qbd_date_driven_terms` (`read`): Returns a list of date-driven terms. NOTE: QuickBooks Desktop does not support pagination for date-driven terms; hence, there is no `cursor` parameter. Users typically have few date-driven terms.
 
 ### Resource `qbd.deleted_list_objects`:
@@ -351,6 +390,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_discount_items` (`write`): Creates a discount item that subtracts either a percentage or fixed amount from transaction totals. Percentage discounts only affect the preceding line, while fixed-amount discounts reduce the accumulated amount above them unless you bound the target lines with a subtotal item.
 - `retrieve_qbd_discount_items` (`read`): Retrieves a discount item by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific discount items by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_discount_items` (`write`): Updates a discount item, including its linked account or discount rate. When changing the account, use `updateExistingTransactionsAccount` to control whether existing transactions that reference the item should also be updated.
 - `list_qbd_discount_items` (`read`): Returns a list of discount items. Use the `cursor` parameter to paginate through the results.
 
@@ -358,6 +400,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_employees` (`write`): Creates an employee record that captures personal details, contact information, employment dates, and payroll settings in a single request so the employee is ready for scheduling, time tracking, and payroll processing.
 - `retrieve_qbd_employees` (`read`): Retrieves an employee by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific employees by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_employees` (`write`): Updates an employee record, allowing you to revise contact details, employment status dates, supervisory assignments, payroll configuration, and additional notes to keep workforce data current.
 - `list_qbd_employees` (`read`): Returns a list of employees. NOTE: QuickBooks Desktop does not support pagination for employees; hence, there is no `cursor` parameter. Users typically have few employees.
 
@@ -366,6 +411,8 @@ The following tools are available in this MCP server.
 - `create_qbd_estimates` (`write`): Creates a new estimate.
 - `retrieve_qbd_estimates` (`read`): Retrieves an estimate by ID.
 
+  **IMPORTANT:** If you need to fetch multiple specific estimates by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
   NOTE: The response automatically includes any linked transactions.
 
 - `update_qbd_estimates` (`write`): Updates an existing estimate.
@@ -376,6 +423,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_inventory_adjustments` (`write`): Creates an inventory adjustment to correct on-hand quantities or values. QuickBooks requires single-user mode unless you're on Enterprise with Advanced Inventory enabled.
 - `retrieve_qbd_inventory_adjustments` (`read`): Retrieves an inventory adjustment by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific inventory adjustments by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_inventory_adjustments` (`write`): Updates an existing inventory adjustment.
 - `list_qbd_inventory_adjustments` (`read`): Returns a list of inventory adjustments. NOTE: QuickBooks Desktop does not support pagination for inventory adjustments; hence, there is no `cursor` parameter. Users typically have few inventory adjustments.
 - `delete_qbd_inventory_adjustments` (`write`): Permanently deletes a an inventory adjustment. The deletion will fail if the inventory adjustment is currently in use or has any linked transactions that are in use.
@@ -384,6 +434,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_inventory_assembly_items` (`write`): Creates an inventory assembly item that bundles existing inventory items.
 - `retrieve_qbd_inventory_assembly_items` (`read`): Retrieves an inventory assembly item by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific inventory assembly items by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_inventory_assembly_items` (`write`): Updates an inventory assembly item. If you change the income account, set `updateExistingTransactionsIncomeAccount` to true so QuickBooks applies the new account to existing transactions that use the assembly.
 - `list_qbd_inventory_assembly_items` (`read`): Returns a list of inventory assembly items. Use the `cursor` parameter to paginate through the results.
 
@@ -391,6 +444,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_inventory_items` (`write`): Creates a new inventory item.
 - `retrieve_qbd_inventory_items` (`read`): Retrieves an inventory item by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific inventory items by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_inventory_items` (`write`): Updates an inventory item. If you switch the income account, set `updateExistingTransactionsIncomeAccount` to true so QuickBooks applies the new account to existing transactions that reference the item.
 - `list_qbd_inventory_items` (`read`): Returns a list of inventory items. Use the `cursor` parameter to paginate through the results.
 
@@ -398,6 +454,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_inventory_sites` (`write`): Creates an inventory site for companies using QuickBooks Enterprise with Advanced Inventory.
 - `retrieve_qbd_inventory_sites` (`read`): Retrieves an inventory site by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific inventory sites by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_inventory_sites` (`write`): Updates an existing inventory site.
 - `list_qbd_inventory_sites` (`read`): Returns a list of inventory sites. NOTE: QuickBooks Desktop does not support pagination for inventory sites; hence, there is no `cursor` parameter. Users typically have few inventory sites.
 
@@ -406,6 +465,8 @@ The following tools are available in this MCP server.
 - `create_qbd_invoices` (`write`): Creates an invoice to bill a customer when goods or services were delivered before payment. Use a sales receipt instead if the sale was paid in full.
 - `retrieve_qbd_invoices` (`read`): Retrieves an invoice by ID.
 
+  **IMPORTANT:** If you need to fetch multiple specific invoices by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
   NOTE: The response automatically includes any linked transactions.
 
 - `update_qbd_invoices` (`write`): Updates an existing invoice.
@@ -416,6 +477,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_item_groups` (`write`): Creates a new item group.
 - `retrieve_qbd_item_groups` (`read`): Retrieves an item group by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific item groups by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_item_groups` (`write`): Updates an existing item group.
 - `list_qbd_item_groups` (`read`): Returns a list of item groups. Use the `cursor` parameter to paginate through the results.
 
@@ -424,6 +488,8 @@ The following tools are available in this MCP server.
 - `create_qbd_item_receipts` (`write`): Creates an item receipt to record inventory received from a vendor. You can link it to a purchase order during creation to pull in the order's lines automatically and update quantities, but that link can't be added later with an update.
 - `retrieve_qbd_item_receipts` (`read`): Retrieves an item receipt by ID.
 
+  **IMPORTANT:** If you need to fetch multiple specific item receipts by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
   NOTE: The response automatically includes any linked transactions.
 
 - `update_qbd_item_receipts` (`write`): Updates an existing item receipt.
@@ -433,12 +499,18 @@ The following tools are available in this MCP server.
 ### Resource `qbd.item_sites`:
 
 - `retrieve_qbd_item_sites` (`read`): Retrieves an item site by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific item sites by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `list_qbd_item_sites` (`read`): Returns a list of item sites. Use the `cursor` parameter to paginate through the results.
 
 ### Resource `qbd.journal_entries`:
 
 - `create_qbd_journal_entries` (`write`): Creates a journal entry with balanced debit and credit lines. QuickBooks Desktop requires total debits to equal total credits, and any line that posts to Accounts Receivable or Accounts Payable must include the related customer or vendor reference.
 - `retrieve_qbd_journal_entries` (`read`): Retrieves a journal entry by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific journal entries by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_journal_entries` (`write`): Updates an existing journal entry. Keep the debits and credits in balance, and include the related customer or vendor on any A/R or A/P line you submit in the update body.
 - `list_qbd_journal_entries` (`read`): Returns a list of journal entries. Use the `cursor` parameter to paginate through the results.
 - `delete_qbd_journal_entries` (`write`): Permanently deletes a a journal entry. The deletion will fail if the journal entry is currently in use or has any linked transactions that are in use.
@@ -447,6 +519,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_non_inventory_items` (`write`): Creates a new non-inventory item.
 - `retrieve_qbd_non_inventory_items` (`read`): Retrieves a non-inventory item by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific non-inventory items by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_non_inventory_items` (`write`): Updates a non-inventory item. You can modify either `salesOrPurchaseDetails` or `salesAndPurchaseDetails`, but the item must keep the same configuration it was created with. When you change `postingAccount`, `incomeAccount`, or `expenseAccount`, include the matching `updateExistingTransactions...` flag so QuickBooks applies the new account to existing transactions and doesn’t reject the update when historical activity is present.
 - `list_qbd_non_inventory_items` (`read`): Returns a list of non-inventory items. Use the `cursor` parameter to paginate through the results.
 
@@ -454,6 +529,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_other_charge_items` (`write`): Creates a new other charge item.
 - `retrieve_qbd_other_charge_items` (`read`): Retrieves an other charge item by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific other charge items by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_other_charge_items` (`write`): Updates an existing other charge item.
 - `list_qbd_other_charge_items` (`read`): Returns a list of other charge items. Use the `cursor` parameter to paginate through the results.
 
@@ -461,6 +539,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_other_names` (`write`): Creates a new other-name.
 - `retrieve_qbd_other_names` (`read`): Retrieves an other-name by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific other-names by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_other_names` (`write`): Updates an existing other-name.
 - `list_qbd_other_names` (`read`): Returns a list of other-names. NOTE: QuickBooks Desktop does not support pagination for other-names; hence, there is no `cursor` parameter. Users typically have few other-names.
 
@@ -468,12 +549,18 @@ The following tools are available in this MCP server.
 
 - `create_qbd_payment_methods` (`write`): Creates a new payment method.
 - `retrieve_qbd_payment_methods` (`read`): Retrieves a payment method by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific payment methods by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `list_qbd_payment_methods` (`read`): Returns a list of payment methods. NOTE: QuickBooks Desktop does not support pagination for payment methods; hence, there is no `cursor` parameter. Users typically have few payment methods.
 
 ### Resource `qbd.payroll_wage_items`:
 
 - `create_qbd_payroll_wage_items` (`write`): Creates a new payroll wage item.
 - `retrieve_qbd_payroll_wage_items` (`read`): Retrieves a payroll wage item by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific payroll wage items by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `list_qbd_payroll_wage_items` (`read`): Returns a list of payroll wage items. Use the `cursor` parameter to paginate through the results.
 
 ### Resource `qbd.preferences`:
@@ -484,6 +571,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_price_levels` (`write`): Creates a new price level.
 - `retrieve_qbd_price_levels` (`read`): Retrieves a price level by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific price levels by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_price_levels` (`write`): Updates an existing price level.
 - `list_qbd_price_levels` (`read`): Returns a list of price levels. NOTE: QuickBooks Desktop does not support pagination for price levels; hence, there is no `cursor` parameter. Users typically have few price levels.
 
@@ -492,6 +582,8 @@ The following tools are available in this MCP server.
 - `create_qbd_purchase_orders` (`write`): Creates a new purchase order.
 - `retrieve_qbd_purchase_orders` (`read`): Retrieves a purchase order by ID.
 
+  **IMPORTANT:** If you need to fetch multiple specific purchase orders by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
   NOTE: The response automatically includes any linked transactions.
 
 - `update_qbd_purchase_orders` (`write`): Updates an existing purchase order.
@@ -502,6 +594,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_receive_payments` (`write`): Records a customer payment and optionally applies it to specific invoices or credits. All allocations must target the same accounts receivable account as those invoices, and each one has to include a payment amount, discount, or credit so QuickBooks can close out the balance.
 - `retrieve_qbd_receive_payments` (`read`): Retrieves a receive-payment by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific receive-payments by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_receive_payments` (`write`): Updates a received payment. When you resubmit applications to invoices, keep them on the same accounts receivable account and include the payment amount, discount, or credit on every allocation you send.
 - `list_qbd_receive_payments` (`read`): Returns a list of receive-payments. Use the `cursor` parameter to paginate through the results.
 - `delete_qbd_receive_payments` (`write`): Permanently deletes a a receive-payment. The deletion will fail if the receive-payment is currently in use or has any linked transactions that are in use.
@@ -511,6 +606,8 @@ The following tools are available in this MCP server.
 - `create_qbd_sales_orders` (`write`): Creates a new sales order.
 - `retrieve_qbd_sales_orders` (`read`): Retrieves a sales order by ID.
 
+  **IMPORTANT:** If you need to fetch multiple specific sales orders by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
   NOTE: The response automatically includes any linked transactions.
 
 - `update_qbd_sales_orders` (`write`): Updates an existing sales order.
@@ -521,6 +618,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_sales_receipts` (`write`): Creates a sales receipt for a sale paid in full. If you include credit card transaction details, QuickBooks requires the payment method to reference a credit card type and automatically deposits the funds to Undeposited Funds rather than a specific bank account.
 - `retrieve_qbd_sales_receipts` (`read`): Retrieves a sales receipt by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific sales receipts by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_sales_receipts` (`write`): Updates an existing sales receipt. Credit card payments still have to use a credit-card payment method and remain deposited to Undeposited Funds, so don’t switch the deposit account in those scenarios.
 - `list_qbd_sales_receipts` (`read`): Returns a list of sales receipts. Use the `cursor` parameter to paginate through the results.
 - `delete_qbd_sales_receipts` (`write`): Permanently deletes a a sales receipt. The deletion will fail if the sales receipt is currently in use or has any linked transactions that are in use.
@@ -529,6 +629,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_sales_representatives` (`write`): Creates a sales representative that references an existing employee, vendor, or other-name record so it can be assigned on sales forms.
 - `retrieve_qbd_sales_representatives` (`read`): Retrieves a sales representative by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific sales representatives by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_sales_representatives` (`write`): Updates an existing sales representative.
 - `list_qbd_sales_representatives` (`read`): Returns a list of sales representatives. NOTE: QuickBooks Desktop does not support pagination for sales representatives; hence, there is no `cursor` parameter. Users typically have few sales representatives.
 
@@ -536,6 +639,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_sales_tax_codes` (`write`): Creates a new sales-tax code.
 - `retrieve_qbd_sales_tax_codes` (`read`): Retrieves a sales-tax code by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific sales-tax codes by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_sales_tax_codes` (`write`): Updates a sales-tax code’s name, activity status, or linked tax items. Once a code has been used you can’t flip it between taxable and non-taxable, and the built-in TAX/NON codes keep their original taxable setting, so plan new codes if you need a different tax status.
 - `list_qbd_sales_tax_codes` (`read`): Returns a list of sales-tax codes. NOTE: QuickBooks Desktop does not support pagination for sales-tax codes; hence, there is no `cursor` parameter. Users typically have few sales-tax codes.
 
@@ -543,6 +649,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_sales_tax_items` (`write`): Creates a new sales-tax item.
 - `retrieve_qbd_sales_tax_items` (`read`): Retrieves a sales-tax item by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific sales-tax items by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_sales_tax_items` (`write`): Updates an existing sales-tax item.
 - `list_qbd_sales_tax_items` (`read`): Returns a list of sales-tax items. Use the `cursor` parameter to paginate through the results.
 
@@ -550,6 +659,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_service_items` (`write`): Creates a new service item.
 - `retrieve_qbd_service_items` (`read`): Retrieves a service item by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific service items by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_service_items` (`write`): Updates a service item’s details, including its accounts and unit-of-measure set. QuickBooks won’t let you convert a sell-only service into a buy-and-sell service (or the reverse); create a separate item instead. If you’re switching the unit of measure, set `forceUnitOfMeasureChange` so QuickBooks replaces it on existing forms.
 - `list_qbd_service_items` (`read`): Returns a list of service items. Use the `cursor` parameter to paginate through the results.
 
@@ -557,12 +669,18 @@ The following tools are available in this MCP server.
 
 - `create_qbd_standard_terms` (`write`): Creates a new standard term.
 - `retrieve_qbd_standard_terms` (`read`): Retrieves a standard term by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific standard terms by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `list_qbd_standard_terms` (`read`): Returns a list of standard terms. NOTE: QuickBooks Desktop does not support pagination for standard terms; hence, there is no `cursor` parameter. Users typically have few standard terms.
 
 ### Resource `qbd.subtotal_items`:
 
 - `create_qbd_subtotal_items` (`write`): Creates a new subtotal item.
 - `retrieve_qbd_subtotal_items` (`read`): Retrieves a subtotal item by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific subtotal items by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_subtotal_items` (`write`): Updates an existing subtotal item.
 - `list_qbd_subtotal_items` (`read`): Returns a list of subtotal items. Use the `cursor` parameter to paginate through the results.
 
@@ -574,6 +692,9 @@ The following tools are available in this MCP server.
 
 - `create_qbd_time_tracking_activities` (`write`): Creates a new time tracking activity.
 - `retrieve_qbd_time_tracking_activities` (`read`): Retrieves a time tracking activity by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific time tracking activities by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_time_tracking_activities` (`write`): Updates an existing time tracking activity.
 - `list_qbd_time_tracking_activities` (`read`): Returns a list of time tracking activities. Use the `cursor` parameter to paginate through the results.
 - `delete_qbd_time_tracking_activities` (`write`): Permanently deletes a a time tracking activity. The deletion will fail if the time tracking activity is currently in use or has any linked transactions that are in use.
@@ -581,12 +702,18 @@ The following tools are available in this MCP server.
 ### Resource `qbd.transactions`:
 
 - `retrieve_qbd_transactions` (`read`): Retrieves a transaction by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific transactions by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `list_qbd_transactions` (`read`): Searches across all transaction types. Unlike transaction-specific queries, this endpoint only returns fields common to all transaction types, such as ID, type, dates, account, and reference numbers. For more details specific to that transaction type, make a subsequent call to the relevant transaction-specific endpoint (such as invoices, bills, etc.). NOTE: This endpoint does not support time tracking activities.
 
 ### Resource `qbd.transfers`:
 
 - `create_qbd_transfers` (`write`): Creates a new transfer.
 - `retrieve_qbd_transfers` (`read`): Retrieves a transfer by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific transfers by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_transfers` (`write`): Updates an existing transfer.
 - `list_qbd_transfers` (`read`): Returns a list of transfers. Use the `cursor` parameter to paginate through the results.
 
@@ -597,6 +724,9 @@ The following tools are available in this MCP server.
   NOTE: The QuickBooks company file must have unit-of-measure enabled (either a single unit per item or multiple units per item). To support both configurations, prefix all UOM set names with "By the" (for example, "By the Barrel"); otherwise, the set may not appear in the QuickBooks UI when the company file is configured for a single unit per item.
 
 - `retrieve_qbd_unit_of_measure_sets` (`read`): Retrieves an unit-of-measure set by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific unit-of-measure sets by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `list_qbd_unit_of_measure_sets` (`read`): Lists all unit-of-measure sets. NOTE: QuickBooks Desktop does not support pagination for unit-of-measure sets; hence, there is no cursor parameter. Users typically have few unit-of-measure sets.
 
   NOTE: The QuickBooks company file must have unit-of-measure enabled (either a single unit per item or multiple units per item).
@@ -606,6 +736,8 @@ The following tools are available in this MCP server.
 - `create_qbd_vendor_credits` (`write`): Creates a vendor credit to capture returns, rebates, or other amounts a vendor owes so you can apply the credit when recording future bill payments.
 - `retrieve_qbd_vendor_credits` (`read`): Retrieves a vendor credit by ID.
 
+  **IMPORTANT:** If you need to fetch multiple specific vendor credits by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
   NOTE: The response automatically includes any linked transactions.
 
 - `update_qbd_vendor_credits` (`write`): Updates a vendor credit before you apply it to bills, letting you adjust the amounts, memo, or line allocations that make up the credit.
@@ -616,5 +748,8 @@ The following tools are available in this MCP server.
 
 - `create_qbd_vendors` (`write`): Creates a new vendor.
 - `retrieve_qbd_vendors` (`read`): Retrieves a vendor by ID.
+
+  **IMPORTANT:** If you need to fetch multiple specific vendors by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.
+
 - `update_qbd_vendors` (`write`): Updates an existing vendor.
 - `list_qbd_vendors` (`read`): Returns a list of vendors. Use the `cursor` parameter to paginate through the results.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "conductor-node-mcp",
-  "version": "12.36.1",
+  "version": "12.38.0",
   "description": "The official MCP Server for the Conductor API",
   "author": "Conductor <support@conductor.is>",
   "types": "./index.d.ts",
@@ -27,7 +27,7 @@
     "fix": "eslint --fix --ext ts,js ."
   },
   "dependencies": {
-    "conductor-node": "^12.36.1",
+    "conductor-node": "^12.38.0",
     "@cloudflare/cabidela": "^0.2.4",
     "@modelcontextprotocol/sdk": "^1.11.5",
     "@valtown/deno-http-worker": "^0.0.21",

package/server.js

@@ -22,7 +22,7 @@ var tools_2 = require("./tools.js");
 Object.defineProperty(exports, "endpoints", { enumerable: true, get: function () { return tools_2.endpoints; } });
 const newMcpServer = () => new mcp_js_1.McpServer({
     name: 'conductor_node_api',
-    version: '12.36.1',
+    version: '12.38.0',
 }, { capabilities: { tools: {}, logging: {} } });
 exports.newMcpServer = newMcpServer;
 // Create server instance

package/server.mjs

@@ -11,7 +11,7 @@ export { ClientType } from "./compat.mjs";
 export { endpoints } from "./tools.mjs";
 export const newMcpServer = () => new McpServer({
     name: 'conductor_node_api',
-    version: '12.36.1',
+    version: '12.38.0',
 }, { capabilities: { tools: {}, logging: {} } });
 // Create server instance
 export const server = newMcpServer();

package/src/server.ts

@@ -33,7 +33,7 @@ export const newMcpServer = () =>
   new McpServer(
     {
       name: 'conductor_node_api',
-      version: '12.36.1',
+      version: '12.38.0',
     },
     { capabilities: { tools: {}, logging: {} } },
   );

package/src/tools/end-users/delete-end-users.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'delete_end_users',
   description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nPermanently deletes an end-user object and all of its connections.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    id: {\n      type: 'string',\n      description: 'The ID of the deleted end-user.'\n    },\n    deleted: {\n      type: 'boolean',\n      description: 'Indicates whether the end-user was deleted.'\n    },\n    objectType: {\n      type: 'string',\n      description: 'The type of object. This value is always `\"end_user\"`.',\n      enum: [        'end_user'\n      ]\n    }\n  },\n  required: [    'id',\n    'deleted',\n    'objectType'\n  ]\n}\n```",
+    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nPermanently deletes an end-user object and all of its connections.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/end_user_delete_response',\n  $defs: {\n    end_user_delete_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The ID of the deleted end-user.'\n        },\n        deleted: {\n          type: 'boolean',\n          description: 'Indicates whether the end-user was deleted.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"end_user\"`.',\n          enum: [            'end_user'\n          ]\n        }\n      },\n      required: [        'id',\n        'deleted',\n        'objectType'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/end-users/list-end-users.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_end_users',
   description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nReturns a list of your end-users.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      description: 'The array of end-users.',\n      items: {\n        $ref: '#/$defs/end_user'\n      }\n    },\n    objectType: {\n      type: 'string',\n      description: 'The type of object. This value is always `\"list\"`.',\n      enum: [        'list'\n      ]\n    },\n    url: {\n      type: 'string',\n      description: 'The endpoint URL where this list can be accessed.'\n    }\n  },\n  required: [    'data',\n    'objectType',\n    'url'\n  ],\n  $defs: {\n    end_user: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier for this end-user. You must save this value to your database because it is how you identify which of your users to receive your API requests.'\n        },\n        companyName: {\n          type: 'string',\n          description: 'The end-user\\'s company name that will be shown elsewhere in Conductor.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this end-user record was created.'\n        },\n        email: {\n          type: 'string',\n          description: 'The end-user\\'s email address for identification purposes.'\n        },\n        integrationConnections: {\n          type: 'array',\n          description: 'The end-user\\'s integration connections.',\n          items: {\n            type: 'object',\n            properties: {\n              id: {\n                type: 'string',\n                description: 'The unique identifier for this integration connection.'\n              },\n              createdAt: {\n                type: 'string',\n                description: 'The date and time when this integration connection record was created.'\n              },\n              integrationSlug: {\n                type: 'string',\n                description: 'The identifier of the third-party platform to integrate.',\n                enum: [                  'quickbooks_desktop'\n                ]\n              },\n              lastRequestAt: {\n                type: 'string',\n                description: 'The date and time of your last API request to this integration connection.'\n              },\n              lastSuccessfulRequestAt: {\n                type: 'string',\n                description: 'The date and time of your last *successful* API request to this integration connection. A successful request means the integration fully processed and returned a response without any errors end-to-end.'\n              },\n              objectType: {\n                type: 'string',\n                description: 'The type of object. This value is always `\"integration_connection\"`.',\n                enum: [                  'integration_connection'\n                ]\n              }\n            },\n            required: [              'id',\n              'createdAt',\n              'integrationSlug',\n              'lastRequestAt',\n              'lastSuccessfulRequestAt',\n              'objectType'\n            ]\n          }\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"end_user\"`.',\n          enum: [            'end_user'\n          ]\n        },\n        sourceId: {\n          type: 'string',\n          description: 'The end-user\\'s unique identifier from your system. Maps users between your database and Conductor.'\n        }\n      },\n      required: [        'id',\n        'companyName',\n        'createdAt',\n        'email',\n        'integrationConnections',\n        'objectType',\n        'sourceId'\n      ]\n    }\n  }\n}\n```",
+    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nReturns a list of your end-users.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/end_user_list_response',\n  $defs: {\n    end_user_list_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'array',\n          description: 'The array of end-users.',\n          items: {\n            $ref: '#/$defs/end_user'\n          }\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"list\"`.',\n          enum: [            'list'\n          ]\n        },\n        url: {\n          type: 'string',\n          description: 'The endpoint URL where this list can be accessed.'\n        }\n      },\n      required: [        'data',\n        'objectType',\n        'url'\n      ]\n    },\n    end_user: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier for this end-user. You must save this value to your database because it is how you identify which of your users to receive your API requests.'\n        },\n        companyName: {\n          type: 'string',\n          description: 'The end-user\\'s company name that will be shown elsewhere in Conductor.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this end-user record was created.'\n        },\n        email: {\n          type: 'string',\n          description: 'The end-user\\'s email address for identification purposes.'\n        },\n        integrationConnections: {\n          type: 'array',\n          description: 'The end-user\\'s integration connections.',\n          items: {\n            type: 'object',\n            properties: {\n              id: {\n                type: 'string',\n                description: 'The unique identifier for this integration connection.'\n              },\n              createdAt: {\n                type: 'string',\n                description: 'The date and time when this integration connection record was created.'\n              },\n              integrationSlug: {\n                type: 'string',\n                description: 'The identifier of the third-party platform to integrate.',\n                enum: [                  'quickbooks_desktop'\n                ]\n              },\n              lastRequestAt: {\n                type: 'string',\n                description: 'The date and time of your last API request to this integration connection.'\n              },\n              lastSuccessfulRequestAt: {\n                type: 'string',\n                description: 'The date and time of your last *successful* API request to this integration connection. A successful request means the integration fully processed and returned a response without any errors end-to-end.'\n              },\n              objectType: {\n                type: 'string',\n                description: 'The type of object. This value is always `\"integration_connection\"`.',\n                enum: [                  'integration_connection'\n                ]\n              }\n            },\n            required: [              'id',\n              'createdAt',\n              'integrationSlug',\n              'lastRequestAt',\n              'lastSuccessfulRequestAt',\n              'objectType'\n            ]\n          }\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"end_user\"`.',\n          enum: [            'end_user'\n          ]\n        },\n        sourceId: {\n          type: 'string',\n          description: 'The end-user\\'s unique identifier from your system. Maps users between your database and Conductor.'\n        }\n      },\n      required: [        'id',\n        'companyName',\n        'createdAt',\n        'email',\n        'integrationConnections',\n        'objectType',\n        'sourceId'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/end-users/passthrough-end-users.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'passthrough_end_users',
   description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nSends a request directly to the specified integration connection (e.g., QuickBooks Desktop) on behalf of the end-user.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  description: 'The response from the integration connection.',\n  additionalProperties: true\n}\n```",
+    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nSends a request directly to the specified integration connection (e.g., QuickBooks Desktop) on behalf of the end-user.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/end_user_passthrough_response',\n  $defs: {\n    end_user_passthrough_response: {\n      type: 'object',\n      description: 'The response from the integration connection.',\n      additionalProperties: true\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/qbd/account-tax-lines/list-qbd-account-tax-lines.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_qbd_account_tax_lines',
   description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nReturns a list of account tax lines. NOTE: QuickBooks Desktop does not support pagination for account tax lines; hence, there is no `cursor` parameter. Users typically have few account tax lines.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      description: 'The array of account tax lines.',\n      items: {\n        $ref: '#/$defs/account_tax_line'\n      }\n    },\n    objectType: {\n      type: 'string',\n      description: 'The type of object. This value is always `\"list\"`.',\n      enum: [        'list'\n      ]\n    },\n    url: {\n      type: 'string',\n      description: 'The endpoint URL where this list can be accessed.'\n    }\n  },\n  required: [    'data',\n    'objectType',\n    'url'\n  ],\n  $defs: {\n    account_tax_line: {\n      type: 'object',\n      title: 'The Account Tax Line object',\n      properties: {\n        taxLineId: {\n          type: 'number',\n          description: 'The identifier of the tax line associated with this account tax line. You can see a list of all available values for this field by calling the endpoint for account tax lines.'\n        },\n        taxLineName: {\n          type: 'string',\n          description: 'The name of the tax line associated with this account tax line, as it appears on the tax form.'\n        }\n      },\n      required: [        'taxLineId',\n        'taxLineName'\n      ]\n    }\n  }\n}\n```",
+    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nReturns a list of account tax lines. NOTE: QuickBooks Desktop does not support pagination for account tax lines; hence, there is no `cursor` parameter. Users typically have few account tax lines.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/account_tax_line_list_response',\n  $defs: {\n    account_tax_line_list_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'array',\n          description: 'The array of account tax lines.',\n          items: {\n            $ref: '#/$defs/account_tax_line'\n          }\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"list\"`.',\n          enum: [            'list'\n          ]\n        },\n        url: {\n          type: 'string',\n          description: 'The endpoint URL where this list can be accessed.'\n        }\n      },\n      required: [        'data',\n        'objectType',\n        'url'\n      ]\n    },\n    account_tax_line: {\n      type: 'object',\n      title: 'The Account Tax Line object',\n      properties: {\n        taxLineId: {\n          type: 'number',\n          description: 'The identifier of the tax line associated with this account tax line. You can see a list of all available values for this field by calling the endpoint for account tax lines.'\n        },\n        taxLineName: {\n          type: 'string',\n          description: 'The name of the tax line associated with this account tax line, as it appears on the tax form.'\n        }\n      },\n      required: [        'taxLineId',\n        'taxLineName'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/qbd/accounts/retrieve-qbd-accounts.ts

@@ -15,7 +15,8 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'retrieve_qbd_accounts',
-  description: 'Retrieves an account by ID.',
+  description:
+    'Retrieves an account by ID.\n\n**IMPORTANT:** If you need to fetch multiple specific accounts by ID, use the list endpoint instead with the `ids` parameter. It accepts an array of IDs so you can batch the request into a single call, which is significantly faster.',
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/qbd/bill-check-payments/delete-qbd-bill-check-payments.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'delete_qbd_bill_check_payments',
   description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nPermanently deletes a a bill check payment. The deletion will fail if the bill check payment is currently in use or has any linked transactions that are in use.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    id: {\n      type: 'string',\n      description: 'The QuickBooks-assigned unique identifier of the deleted bill check payment.'\n    },\n    deleted: {\n      type: 'boolean',\n      description: 'Indicates whether the bill check payment was deleted.'\n    },\n    objectType: {\n      type: 'string',\n      description: 'The type of object. This value is always `\"qbd_bill_check_payment\"`.',\n      enum: [        'qbd_bill_check_payment'\n      ]\n    },\n    refNumber: {\n      type: 'string',\n      description: 'The case-sensitive user-defined reference number of the deleted bill check payment.'\n    }\n  },\n  required: [    'id',\n    'deleted',\n    'objectType',\n    'refNumber'\n  ]\n}\n```",
+    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nPermanently deletes a a bill check payment. The deletion will fail if the bill check payment is currently in use or has any linked transactions that are in use.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/bill_check_payment_delete_response',\n  $defs: {\n    bill_check_payment_delete_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The QuickBooks-assigned unique identifier of the deleted bill check payment.'\n        },\n        deleted: {\n          type: 'boolean',\n          description: 'Indicates whether the bill check payment was deleted.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_bill_check_payment\"`.',\n          enum: [            'qbd_bill_check_payment'\n          ]\n        },\n        refNumber: {\n          type: 'string',\n          description: 'The case-sensitive user-defined reference number of the deleted bill check payment.'\n        }\n      },\n      required: [        'id',\n        'deleted',\n        'objectType',\n        'refNumber'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {