conductor-node-mcp 13.1.0 → 14.0.0

package/src/tools/qbd/bill-credit-card-payments/list-qbd-bill-credit-card-payments.ts

@@ -1,147 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asErrorResult, asTextContentResult } from 'conductor-node-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Conductor from 'conductor-node';
-
-export const metadata: Metadata = {
-  resource: 'qbd.bill_credit_card_payments',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/quickbooks-desktop/bill-credit-card-payments',
-};
-
-export const tool: Tool = {
-  name: 'list_qbd_bill_credit_card_payments',
-  description:
-    'Returns a list of bill credit card payments. Use the `cursor` parameter to paginate through the results.',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      conductorEndUserId: {
-        type: 'string',
-        description: 'The ID of the End-User to receive this request.',
-      },
-      accountIds: {
-        type: 'array',
-        description: 'Filter for bill credit card payments associated with these accounts.',
-        items: {
-          type: 'string',
-        },
-      },
-      currencyIds: {
-        type: 'array',
-        description: 'Filter for bill credit card payments in these currencies.',
-        items: {
-          type: 'string',
-        },
-      },
-      cursor: {
-        type: 'string',
-        description:
-          'The pagination token to fetch the next set of results when paginating with the `limit` parameter. Do not include this parameter on the first call. Use the `nextCursor` value returned in the previous response to request subsequent results.',
-      },
-      ids: {
-        type: 'array',
-        description:
-          'Filter for specific bill credit card payments by their QuickBooks-assigned unique identifier(s).\n\n**IMPORTANT**: If you include this parameter, QuickBooks will ignore all other query parameters for this request.\n\n**NOTE**: If any of the values you specify in this parameter are not found, the request will return an error.',
-        items: {
-          type: 'string',
-        },
-      },
-      includeLineItems: {
-        type: 'boolean',
-        description: 'Whether to include line items in the response. Defaults to `true`.',
-      },
-      limit: {
-        type: 'integer',
-        description:
-          'The maximum number of objects to return. Accepts values ranging from 1 to 150, defaults to 150. When used with cursor-based pagination, this parameter controls how many results are returned per page. To paginate through results, combine this with the `cursor` parameter. Each response will include a `nextCursor` value that can be passed to subsequent requests to retrieve the next page of results.',
-      },
-      refNumberContains: {
-        type: 'string',
-        description:
-          'Filter for bill credit card payments whose `refNumber` contains this substring.\n\n**NOTE**: If you use this parameter, you cannot also use `refNumberStartsWith` or `refNumberEndsWith`.',
-      },
-      refNumberEndsWith: {
-        type: 'string',
-        description:
-          'Filter for bill credit card payments whose `refNumber` ends with this substring.\n\n**NOTE**: If you use this parameter, you cannot also use `refNumberContains` or `refNumberStartsWith`.',
-      },
-      refNumberFrom: {
-        type: 'string',
-        description:
-          'Filter for bill credit card payments whose `refNumber` is greater than or equal to this value. If omitted, the range will begin with the first number of the list. Uses a numerical comparison for values that contain only digits; otherwise, uses a lexicographical comparison.',
-      },
-      refNumbers: {
-        type: 'array',
-        description:
-          'Filter for specific bill credit card payments by their ref-number(s), case-sensitive. In QuickBooks, ref-numbers are not required to be unique and can be arbitrarily changed by the QuickBooks user.\n\n**IMPORTANT**: If you include this parameter, QuickBooks will ignore all other query parameters for this request.\n\n**NOTE**: If any of the values you specify in this parameter are not found, the request will return an error.',
-        items: {
-          type: 'string',
-        },
-      },
-      refNumberStartsWith: {
-        type: 'string',
-        description:
-          'Filter for bill credit card payments whose `refNumber` starts with this substring.\n\n**NOTE**: If you use this parameter, you cannot also use `refNumberContains` or `refNumberEndsWith`.',
-      },
-      refNumberTo: {
-        type: 'string',
-        description:
-          'Filter for bill credit card payments whose `refNumber` is less than or equal to this value. If omitted, the range will end with the last number of the list. Uses a numerical comparison for values that contain only digits; otherwise, uses a lexicographical comparison.',
-      },
-      transactionDateFrom: {
-        type: 'string',
-        description:
-          "Filter for bill credit card payments whose `date` field is on or after this date, in ISO 8601 format (YYYY-MM-DD).\n\n**NOTE:** QuickBooks Desktop interprets this date as the **start of the specified day** in the local timezone of the end-user's computer (e.g., `2025-01-01` → `2025-01-01T00:00:00`).",
-        format: 'date',
-      },
-      transactionDateTo: {
-        type: 'string',
-        description:
-          "Filter for bill credit card payments whose `date` field is on or before this date, in ISO 8601 format (YYYY-MM-DD).\n\n**NOTE:** QuickBooks Desktop interprets this date as the **end of the specified day** in the local timezone of the end-user's computer (e.g., `2025-01-01` → `2025-01-01T23:59:59`).",
-        format: 'date',
-      },
-      updatedAfter: {
-        type: 'string',
-        description:
-          "Filter for bill credit card payments updated on or after this date/time. Accepts the following ISO 8601 formats:\n- **date-only** (YYYY-MM-DD) - QuickBooks Desktop interprets the date as the **start of the specified day** in the local timezone of the end-user's computer (e.g., `2025-01-01` → `2025-01-01T00:00:00`).\n- **datetime without timezone** (YYYY-MM-DDTHH:mm:ss) - QuickBooks Desktop interprets the timestamp in the local timezone of the end-user's computer.\n- **datetime with timezone** (YYYY-MM-DDTHH:mm:ss±HH:mm) - QuickBooks Desktop interprets the timestamp using the specified timezone.",
-      },
-      updatedBefore: {
-        type: 'string',
-        description:
-          "Filter for bill credit card payments updated on or before this date/time. Accepts the following ISO 8601 formats:\n- **date-only** (YYYY-MM-DD) - QuickBooks Desktop interprets the date as the **end of the specified day** in the local timezone of the end-user's computer (e.g., `2025-01-01` → `2025-01-01T23:59:59`).\n- **datetime without timezone** (YYYY-MM-DDTHH:mm:ss) - QuickBooks Desktop interprets the timestamp in the local timezone of the end-user's computer.\n- **datetime with timezone** (YYYY-MM-DDTHH:mm:ss±HH:mm) - QuickBooks Desktop interprets the timestamp using the specified timezone.",
-      },
-      vendorIds: {
-        type: 'array',
-        description:
-          'Filter for bill credit card payments sent to these vendors. These are the vendors who sent the bills paid by these credit card payments.',
-        items: {
-          type: 'string',
-        },
-      },
-    },
-    required: ['conductorEndUserId'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (conductor: Conductor, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await conductor.qbd.billCreditCardPayments.list(body).asResponse();
-  try {
-    return asTextContentResult(await response.json());
-  } catch (error) {
-    if (error instanceof Conductor.APIError) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/qbd/bill-credit-card-payments/retrieve-qbd-bill-credit-card-payments.ts

@@ -1,51 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asErrorResult, asTextContentResult } from 'conductor-node-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Conductor from 'conductor-node';
-
-export const metadata: Metadata = {
-  resource: 'qbd.bill_credit_card_payments',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/quickbooks-desktop/bill-credit-card-payments/{id}',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_qbd_bill_credit_card_payments',
-  description:
-    'Retrieves a bill credit card payment by ID.\n\n**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.',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      id: {
-        type: 'string',
-        description: 'The QuickBooks-assigned unique identifier of the bill credit card payment to retrieve.',
-      },
-      conductorEndUserId: {
-        type: 'string',
-        description: 'The ID of the End-User to receive this request.',
-      },
-    },
-    required: ['id', 'conductorEndUserId'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (conductor: Conductor, args: Record<string, unknown> | undefined) => {
-  const { id, ...body } = args as any;
-  try {
-    return asTextContentResult(await conductor.qbd.billCreditCardPayments.retrieve(id, body));
-  } catch (error) {
-    if (error instanceof Conductor.APIError) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/qbd/bills/create-qbd-bills.ts

@@ -1,422 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asErrorResult, asTextContentResult } from 'conductor-node-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Conductor from 'conductor-node';
-
-export const metadata: Metadata = {
-  resource: 'qbd.bills',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/quickbooks-desktop/bills',
-};
-
-export const tool: Tool = {
-  name: 'create_qbd_bills',
-  description:
-    "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.",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      transactionDate: {
-        type: 'string',
-        description: 'The date of this bill, in ISO 8601 format (YYYY-MM-DD).',
-        format: 'date',
-      },
-      vendorId: {
-        type: 'string',
-        description: 'The vendor who sent this bill for goods or services purchased.',
-      },
-      conductorEndUserId: {
-        type: 'string',
-        description: 'The ID of the End-User to receive this request.',
-      },
-      dueDate: {
-        type: 'string',
-        description: 'The date by which this bill must be paid, in ISO 8601 format (YYYY-MM-DD).',
-        format: 'date',
-      },
-      exchangeRate: {
-        type: 'number',
-        description:
-          "The market exchange rate between this bill's currency and the home currency in QuickBooks at the time of this transaction. Represented as a decimal value (e.g., 1.2345 for 1 EUR = 1.2345 USD if USD is the home currency).",
-      },
-      expenseLines: {
-        type: 'array',
-        description: "The bill's expense lines, each representing one line in this expense.",
-        items: {
-          type: 'object',
-          properties: {
-            accountId: {
-              type: 'string',
-              description:
-                'The expense account being debited (increased) for this expense line. The corresponding account being credited is usually a liability account (e.g., Accounts-Payable) or an asset account (e.g., Cash), depending on the transaction type.',
-            },
-            amount: {
-              type: 'string',
-              description: 'The monetary amount of this expense line, represented as a decimal string.',
-            },
-            billingStatus: {
-              type: 'string',
-              description: 'The billing status of this expense line.',
-              enum: ['billable', 'has_been_billed', 'not_billable'],
-            },
-            classId: {
-              type: 'string',
-              description:
-                "The expense line's class. Classes can be used to categorize objects into meaningful segments, such as department, location, or type of work. In QuickBooks, class tracking is off by default. If a class is specified for the entire parent transaction, it is automatically applied to all expense lines unless overridden here, at the transaction line level.",
-            },
-            customFields: {
-              type: 'array',
-              description:
-                'The custom fields for the expense line object, added as user-defined data extensions, not included in the standard QuickBooks object.',
-              items: {
-                type: 'object',
-                properties: {
-                  name: {
-                    type: 'string',
-                    description:
-                      'The name of the custom field, unique for the specified `ownerId`. For public custom fields, this name is visible as a label in the QuickBooks UI.',
-                  },
-                  ownerId: {
-                    type: 'string',
-                    description:
-                      'The identifier of the owner of the custom field, which QuickBooks internally calls a "data extension". For public custom fields visible in the UI, such as those added by the QuickBooks user, this is always "0". For private custom fields that are only visible to the application that created them, this is a valid GUID identifying the owning application. Internally, Conductor always fetches all public custom fields (those with an `ownerId` of "0") for all objects.',
-                  },
-                  value: {
-                    type: 'string',
-                    description:
-                      "The value of this custom field. The maximum length depends on the field's data type.",
-                  },
-                },
-                required: ['name', 'ownerId', 'value'],
-              },
-            },
-            memo: {
-              type: 'string',
-              description: 'A memo or note for this expense line.',
-            },
-            payeeId: {
-              type: 'string',
-              description:
-                "If `account` refers to an Accounts-Payable (A/P) account, `payee` refers to the expense's vendor (not the customer). If `account` refers to any other type of account, `payee` refers to the expense's customer (not the vendor).",
-            },
-            salesRepresentativeId: {
-              type: 'string',
-              description:
-                "The expense line's sales representative. Sales representatives can be employees, vendors, or other names in QuickBooks.",
-            },
-            salesTaxCodeId: {
-              type: 'string',
-              description:
-                'The sales-tax code for this expense line, determining whether it is taxable or non-taxable. If set, this overrides any sales-tax codes defined on the parent transaction or the associated item.\n\nDefault codes include "Non" (non-taxable) and "Tax" (taxable), but custom codes can also be created in QuickBooks. If QuickBooks is not set up to charge sales tax (via the "Do You Charge Sales Tax?" preference), it will assign the default non-taxable code to all sales.',
-            },
-          },
-        },
-      },
-      externalId: {
-        type: 'string',
-        description:
-          'A globally unique identifier (GUID) you, the developer, can provide for tracking this object in your external system. This field is immutable and can only be set during object creation.\n\n**IMPORTANT**: This field must be formatted as a valid GUID; otherwise, QuickBooks will return an error.',
-      },
-      itemGroupLines: {
-        type: 'array',
-        description:
-          "The bill's item group lines, each representing a predefined set of items bundled together because they are commonly purchased together or grouped for faster entry.",
-        items: {
-          type: 'object',
-          properties: {
-            itemGroupId: {
-              type: 'string',
-              description:
-                "The item group line's item group, representing a predefined set of items bundled because they are commonly purchased together or grouped for faster entry.",
-            },
-            customFields: {
-              type: 'array',
-              description:
-                'The custom fields for the item group line object, added as user-defined data extensions, not included in the standard QuickBooks object.',
-              items: {
-                type: 'object',
-                properties: {
-                  name: {
-                    type: 'string',
-                    description:
-                      'The name of the custom field, unique for the specified `ownerId`. For public custom fields, this name is visible as a label in the QuickBooks UI.',
-                  },
-                  ownerId: {
-                    type: 'string',
-                    description:
-                      'The identifier of the owner of the custom field, which QuickBooks internally calls a "data extension". For public custom fields visible in the UI, such as those added by the QuickBooks user, this is always "0". For private custom fields that are only visible to the application that created them, this is a valid GUID identifying the owning application. Internally, Conductor always fetches all public custom fields (those with an `ownerId` of "0") for all objects.',
-                  },
-                  value: {
-                    type: 'string',
-                    description:
-                      "The value of this custom field. The maximum length depends on the field's data type.",
-                  },
-                },
-                required: ['name', 'ownerId', 'value'],
-              },
-            },
-            inventorySiteId: {
-              type: 'string',
-              description:
-                'The site location where inventory for the item group associated with this item group line is stored.',
-            },
-            inventorySiteLocationId: {
-              type: 'string',
-              description:
-                'The specific location (e.g., bin or shelf) within the inventory site where the item group associated with this item group line is stored.',
-            },
-            quantity: {
-              type: 'number',
-              description:
-                'The quantity of the item group associated with this item group line. This field cannot be cleared.\n\n**NOTE**: Do not use this field if the associated item group is a discount item group.',
-            },
-            unitOfMeasure: {
-              type: 'string',
-              description:
-                "The unit-of-measure used for the `quantity` in this item group line. Must be a valid unit within the item's available units of measure.",
-            },
-          },
-          required: ['itemGroupId'],
-        },
-      },
-      itemLines: {
-        type: 'array',
-        description: "The bill's item lines, each representing the purchase of a specific item or service.",
-        items: {
-          type: 'object',
-          properties: {
-            amount: {
-              type: 'string',
-              description:
-                'The monetary amount of this item line, represented as a decimal string. If both `quantity` and `cost` are specified but not `amount`, QuickBooks will use them to calculate `amount`. If `amount`, `cost`, and `quantity` are all unspecified, then QuickBooks will calculate `amount` based on a `quantity` of `1` and the suggested `cost`. This field cannot be cleared.',
-            },
-            billingStatus: {
-              type: 'string',
-              description: 'The billing status of this item line.',
-              enum: ['billable', 'has_been_billed', 'not_billable'],
-            },
-            classId: {
-              type: 'string',
-              description:
-                "The item line's class. Classes can be used to categorize objects into meaningful segments, such as department, location, or type of work. In QuickBooks, class tracking is off by default. If a class is specified for the entire parent transaction, it is automatically applied to all item lines unless overridden here, at the transaction line level.",
-            },
-            cost: {
-              type: 'string',
-              description:
-                'The cost of this item line, represented as a decimal string. If both `quantity` and `amount` are specified but not `cost`, QuickBooks will use them to calculate `cost`.',
-            },
-            customerId: {
-              type: 'string',
-              description: 'The customer or customer-job associated with this item line.',
-            },
-            customFields: {
-              type: 'array',
-              description:
-                'The custom fields for the item line object, added as user-defined data extensions, not included in the standard QuickBooks object.',
-              items: {
-                type: 'object',
-                properties: {
-                  name: {
-                    type: 'string',
-                    description:
-                      'The name of the custom field, unique for the specified `ownerId`. For public custom fields, this name is visible as a label in the QuickBooks UI.',
-                  },
-                  ownerId: {
-                    type: 'string',
-                    description:
-                      'The identifier of the owner of the custom field, which QuickBooks internally calls a "data extension". For public custom fields visible in the UI, such as those added by the QuickBooks user, this is always "0". For private custom fields that are only visible to the application that created them, this is a valid GUID identifying the owning application. Internally, Conductor always fetches all public custom fields (those with an `ownerId` of "0") for all objects.',
-                  },
-                  value: {
-                    type: 'string',
-                    description:
-                      "The value of this custom field. The maximum length depends on the field's data type.",
-                  },
-                },
-                required: ['name', 'ownerId', 'value'],
-              },
-            },
-            description: {
-              type: 'string',
-              description: 'A description of this item line.',
-            },
-            expirationDate: {
-              type: 'string',
-              description:
-                'The expiration date for the serial number or lot number of the item associated with this item line, in ISO 8601 format (YYYY-MM-DD). This is particularly relevant for perishable or time-sensitive inventory items. Note that this field is only supported on QuickBooks Desktop 2023 or later.',
-              format: 'date',
-            },
-            inventorySiteId: {
-              type: 'string',
-              description:
-                'The site location where inventory for the item associated with this item line is stored.',
-            },
-            inventorySiteLocationId: {
-              type: 'string',
-              description:
-                'The specific location (e.g., bin or shelf) within the inventory site where the item associated with this item line is stored.',
-            },
-            itemId: {
-              type: 'string',
-              description:
-                'The item associated with this item line. This can refer to any good or service that the business buys or sells, including item types such as a service item, inventory item, or special calculation item like a discount item or sales-tax item.',
-            },
-            linkToTransactionLine: {
-              type: 'object',
-              description:
-                "An existing transaction line that you wish to link to this item line. Note that this only links to a single transaction line item, not an entire transaction. If you want to link an entire transaction and bring in all its lines, instead use the field `linkToTransactionIds` on the parent transaction, if available. If the parent transaction is a bill or an item receipt, you can only link to purchase orders; QuickBooks does not support linking these transactions to other transaction types.\n\nTransaction lines can only be linked when creating this item line and cannot be unlinked later.\n\n**IMPORTANT**: If you use `linkToTransactionLine` on this item line, you cannot use the field `item` on this line (QuickBooks will return an error) because this field brings in all of the item information you need. You can, however, specify whatever `quantity` or `rate` that you want, or any other transaction line element other than `item`.\n\nIf the parent transaction supports the `linkToTransactionIds` field, you can use both `linkToTransactionLine` (on this item line) and `linkToTransactionIds` (on its parent transaction) in the same request as long as they do NOT link to the same transaction (otherwise, QuickBooks will return an error). QuickBooks will also return an error if you attempt to link a transaction that is empty or already closed.\n\n**IMPORTANT**: By default, QuickBooks will not return any information about the linked transaction line in this endpoint's response even when this request is successful. To see the transaction line linked via this field, refetch the parent transaction and check the `linkedTransactions` response field. If fetching a list of transactions, you must also specify the parameter `includeLinkedTransactions=true` to see the `linkedTransactions` response field.",
-              properties: {
-                transactionId: {
-                  type: 'string',
-                  description: 'The ID of the transaction to which to link this transaction.',
-                },
-                transactionLineId: {
-                  type: 'string',
-                  description: 'The ID of the transaction line to which to link this transaction.',
-                },
-              },
-              required: ['transactionId', 'transactionLineId'],
-            },
-            lotNumber: {
-              type: 'string',
-              description:
-                'The lot number of the item associated with this item line. Used for tracking groups of inventory items that are purchased or manufactured together.',
-            },
-            overrideItemAccountId: {
-              type: 'string',
-              description:
-                'The account to use for this item line, overriding the default account associated with the item.',
-            },
-            quantity: {
-              type: 'number',
-              description:
-                'The quantity of the item associated with this item line. This field cannot be cleared.\n\n**NOTE**: Do not use this field if the associated item is a discount item.',
-            },
-            salesRepresentativeId: {
-              type: 'string',
-              description:
-                "The item line's sales representative. Sales representatives can be employees, vendors, or other names in QuickBooks.",
-            },
-            salesTaxCodeId: {
-              type: 'string',
-              description:
-                'The sales-tax code for this item line, determining whether it is taxable or non-taxable. If set, this overrides any sales-tax codes defined on the parent transaction or the associated item.\n\nDefault codes include "Non" (non-taxable) and "Tax" (taxable), but custom codes can also be created in QuickBooks. If QuickBooks is not set up to charge sales tax (via the "Do You Charge Sales Tax?" preference), it will assign the default non-taxable code to all sales.',
-            },
-            serialNumber: {
-              type: 'string',
-              description:
-                'The serial number of the item associated with this item line. This is used for tracking individual units of serialized inventory items.',
-            },
-            unitOfMeasure: {
-              type: 'string',
-              description:
-                "The unit-of-measure used for the `quantity` in this item line. Must be a valid unit within the item's available units of measure.",
-            },
-          },
-        },
-      },
-      linkToTransactionIds: {
-        type: 'array',
-        description:
-          "IDs of existing purchase orders that you wish to link to this bill. Note that this links entire transactions, not individual transaction lines. If you want to link individual lines in a transaction, instead use the field `linkToTransactionLine` on this bill's lines, if available.\n\nTransactions can only be linked when creating this bill and cannot be unlinked later.\n\nYou can use both `linkToTransactionIds` (on this bill) and `linkToTransactionLine` (on its transaction lines) as long as they do NOT link to the same transaction (otherwise, QuickBooks will return an error). QuickBooks will also return an error if you attempt to link a transaction that is empty or already closed.\n\n**IMPORTANT**: By default, QuickBooks will not return any information about the linked transactions in this endpoint's response even when this request is successful. To see the transactions linked via this field, refetch the bill and check the `linkedTransactions` response field. If fetching a list of bills, you must also specify the parameter `includeLinkedTransactions=true` to see the `linkedTransactions` response field.",
-        items: {
-          type: 'string',
-        },
-      },
-      memo: {
-        type: 'string',
-        description:
-          'A memo or note for this bill that appears in the Accounts-Payable register and in reports that include this bill.',
-      },
-      payablesAccountId: {
-        type: 'string',
-        description:
-          'The Accounts-Payable (A/P) account to which this bill is assigned, used to track the amount owed. If not specified, QuickBooks Desktop will use its default A/P account.\n\n**IMPORTANT**: If this bill is linked to other transactions, this A/P account must match the `payablesAccount` used in those other transactions.',
-      },
-      refNumber: {
-        type: 'string',
-        description:
-          'The case-sensitive user-defined reference number for this bill, which can be used to identify the transaction in QuickBooks. This value is not required to be unique and can be arbitrarily changed by the QuickBooks user. When left blank in this create request, this field will be left blank in QuickBooks (i.e., it does *not* auto-increment).',
-      },
-      salesTaxCodeId: {
-        type: 'string',
-        description:
-          'The sales-tax code for this bill, determining whether it is taxable or non-taxable. If set, this overrides any sales-tax codes defined on the vendor. This can be overridden on the bill\'s individual lines.\n\nDefault codes include "Non" (non-taxable) and "Tax" (taxable), but custom codes can also be created in QuickBooks. If QuickBooks is not set up to charge sales tax (via the "Do You Charge Sales Tax?" preference), it will assign the default non-taxable code to all sales.',
-      },
-      termsId: {
-        type: 'string',
-        description: "The bill's payment terms, defining when payment is due and any applicable discounts.",
-      },
-      vendorAddress: {
-        type: 'object',
-        description: 'The address of the vendor who sent this bill.',
-        properties: {
-          city: {
-            type: 'string',
-            description:
-              'The city, district, suburb, town, or village name of the address.\n\nMaximum length: 31 characters.',
-          },
-          country: {
-            type: 'string',
-            description: 'The country name of the address.',
-          },
-          line1: {
-            type: 'string',
-            description:
-              'The first line of the address (e.g., street, PO Box, or company name).\n\nMaximum length: 41 characters.',
-          },
-          line2: {
-            type: 'string',
-            description:
-              'The second line of the address, if needed (e.g., apartment, suite, unit, or building).\n\nMaximum length: 41 characters.',
-          },
-          line3: {
-            type: 'string',
-            description: 'The third line of the address, if needed.\n\nMaximum length: 41 characters.',
-          },
-          line4: {
-            type: 'string',
-            description: 'The fourth line of the address, if needed.\n\nMaximum length: 41 characters.',
-          },
-          line5: {
-            type: 'string',
-            description: 'The fifth line of the address, if needed.\n\nMaximum length: 41 characters.',
-          },
-          note: {
-            type: 'string',
-            description:
-              'A note written at the bottom of the address in the form in which it appears, such as the invoice form.',
-          },
-          postalCode: {
-            type: 'string',
-            description: 'The postal code or ZIP code of the address.\n\nMaximum length: 13 characters.',
-          },
-          state: {
-            type: 'string',
-            description:
-              'The state, county, province, or region name of the address.\n\nMaximum length: 21 characters.',
-          },
-        },
-      },
-    },
-    required: ['transactionDate', 'vendorId', 'conductorEndUserId'],
-  },
-  annotations: {},
-};
-
-export const handler = async (conductor: Conductor, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  try {
-    return asTextContentResult(await conductor.qbd.bills.create(body));
-  } catch (error) {
-    if (error instanceof Conductor.APIError) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };