conductor-node-mcp 12.28.0 → 12.30.0

package/src/tools/qbd/classes/update-qbd-classes.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'update_qbd_classes',
   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\nUpdates an existing class.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/class',\n  $defs: {\n    class: {\n      type: 'object',\n      title: 'The Class object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this class. This ID is unique across all classes but not across different QuickBooks object types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this class was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        },\n        fullName: {\n          type: 'string',\n          description: 'The case-insensitive fully-qualified unique name of this class, formed by combining the names of its hierarchical parent objects with its own `name`, separated by colons. For example, if a class is under \"Department\" and has the `name` \"Marketing\", its `fullName` would be \"Department:Marketing\".\\n\\n**NOTE**: Unlike `name`, `fullName` is guaranteed to be unique across all class objects. However, `fullName` can still be arbitrarily changed by the QuickBooks user when they modify the underlying `name` field.'\n        },\n        isActive: {\n          type: 'boolean',\n          description: 'Indicates whether this class is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`.'\n        },\n        name: {\n          type: 'string',\n          description: 'The case-insensitive name of this class. Not guaranteed to be unique because it does not include the names of its hierarchical parent objects like `fullName` does. For example, two classes could both have the `name` \"Marketing\", but they could have unique `fullName` values, such as \"Department:Marketing\" and \"Internal:Marketing\".'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_class\"`.',\n          enum: [            'qbd_class'\n          ]\n        },\n        parent: {\n          type: 'object',\n          description: 'The parent class one level above this one in the hierarchy. For example, if this class has a `fullName` of \"Department:Marketing\", its parent has a `fullName` of \"Department\". If this class is at the top level, this field will be `null`.',\n          properties: {\n            id: {\n              type: 'string',\n              description: 'The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types.'\n            },\n            fullName: {\n              type: 'string',\n              description: 'The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive.'\n            }\n          },\n          required: [            'id',\n            'fullName'\n          ]\n        },\n        revisionNumber: {\n          type: 'string',\n          description: 'The current QuickBooks-assigned revision number of this class object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you\\'re working with the latest data; otherwise, the update will return an error.'\n        },\n        sublevel: {\n          type: 'number',\n          description: 'The depth level of this class in the hierarchy. A top-level class has a `sublevel` of 0; each subsequent sublevel increases this number by 1. For example, a class with a `fullName` of \"Department:Marketing\" would have a `sublevel` of 1.'\n        },\n        updatedAt: {\n          type: 'string',\n          description: 'The date and time when this class was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'fullName',\n        'isActive',\n        'name',\n        'objectType',\n        'parent',\n        'revisionNumber',\n        'sublevel',\n        'updatedAt'\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\nUpdates an existing class.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/class',\n  $defs: {\n    class: {\n      type: 'object',\n      title: 'The Class object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this class. This ID is unique across all classes but not across different QuickBooks object types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this class was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        },\n        fullName: {\n          type: 'string',\n          description: 'The case-insensitive fully-qualified unique name of this class, formed by combining the names of its hierarchical parent objects with its own `name`, separated by colons. For example, if a class is under \"Department\" and has the `name` \"Marketing\", its `fullName` would be \"Department:Marketing\".\\n\\n**NOTE**: Unlike `name`, `fullName` is guaranteed to be unique across all class objects. However, `fullName` can still be arbitrarily changed by the QuickBooks user when they modify the underlying `name` field.'\n        },\n        isActive: {\n          type: 'boolean',\n          description: 'Indicates whether this class is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`.'\n        },\n        name: {\n          type: 'string',\n          description: 'The case-insensitive name of this class. Not guaranteed to be unique because it does not include the names of its hierarchical parent objects like `fullName` does. For example, two classes could both have the `name` \"Marketing\", but they could have unique `fullName` values, such as \"Department:Marketing\" and \"Internal:Marketing\".'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_class\"`.',\n          enum: [            'qbd_class'\n          ]\n        },\n        parent: {\n          type: 'object',\n          description: 'The parent class one level above this one in the hierarchy. For example, if this class has a `fullName` of \"Department:Marketing\", its parent has a `fullName` of \"Department\". If this class is at the top level, this field will be `null`.',\n          properties: {\n            id: {\n              type: 'string',\n              description: 'The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types.'\n            },\n            fullName: {\n              type: 'string',\n              description: 'The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive.'\n            }\n          },\n          required: [            'id',\n            'fullName'\n          ]\n        },\n        revisionNumber: {\n          type: 'string',\n          description: 'The current QuickBooks-assigned revision number of this class object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you\\'re working with the latest data; otherwise, the update will return an error.'\n        },\n        sublevel: {\n          type: 'number',\n          description: 'The depth level of this class in the hierarchy. A top-level class has a `sublevel` of 0; each subsequent sublevel increases this number by 1. For example, a class with a `fullName` of \"Department:Marketing\" would have a `sublevel` of 1.'\n        },\n        updatedAt: {\n          type: 'string',\n          description: 'The date and time when this class was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'fullName',\n        'isActive',\n        'name',\n        'objectType',\n        'parent',\n        'revisionNumber',\n        'sublevel',\n        'updatedAt'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/qbd/credit-card-charges/list-qbd-credit-card-charges.ts

@@ -105,24 +105,24 @@ export const tool: Tool = {
       transactionDateFrom: {
         type: 'string',
         description:
-          'Filter for credit card charges whose `date` field is on or after this date, in ISO 8601 format (YYYY-MM-DD).',
+          "Filter for credit card charges 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 credit card charges whose `date` field is on or before this date, in ISO 8601 format (YYYY-MM-DD).',
+          "Filter for credit card charges 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 credit card charges updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for credit card charges 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 credit card charges updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for credit card charges 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.",
       },
     },
     required: ['conductorEndUserId'],

package/src/tools/qbd/credit-card-credits/list-qbd-credit-card-credits.ts

@@ -105,24 +105,24 @@ export const tool: Tool = {
       transactionDateFrom: {
         type: 'string',
         description:
-          'Filter for credit card credits whose `date` field is on or after this date, in ISO 8601 format (YYYY-MM-DD).',
+          "Filter for credit card credits 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 credit card credits whose `date` field is on or before this date, in ISO 8601 format (YYYY-MM-DD).',
+          "Filter for credit card credits 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 credit card credits updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for credit card credits 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 credit card credits updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for credit card credits 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.",
       },
     },
     required: ['conductorEndUserId'],

package/src/tools/qbd/credit-memos/list-qbd-credit-memos.ts

@@ -109,24 +109,24 @@ export const tool: Tool = {
       transactionDateFrom: {
         type: 'string',
         description:
-          'Filter for credit memos whose `date` field is on or after this date, in ISO 8601 format (YYYY-MM-DD).',
+          "Filter for credit memos 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 credit memos whose `date` field is on or before this date, in ISO 8601 format (YYYY-MM-DD).',
+          "Filter for credit memos 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 credit memos updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for credit memos 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 credit memos updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for credit memos 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.",
       },
     },
     required: ['conductorEndUserId'],

package/src/tools/qbd/customers/list-qbd-customers.ts

@@ -122,12 +122,12 @@ export const tool: Tool = {
       updatedAfter: {
         type: 'string',
         description:
-          'Filter for customers updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for customers 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 customers updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for customers 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.",
       },
     },
     required: ['conductorEndUserId'],

package/src/tools/qbd/date-driven-terms/create-qbd-date-driven-terms.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'create_qbd_date_driven_terms',
   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\nCreates a new date-driven term.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/date_driven_term',\n  $defs: {\n    date_driven_term: {\n      type: 'object',\n      title: 'The Date-Driven Term object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this date-driven term. This ID is unique across all date-driven terms but not across different QuickBooks object types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        },\n        discountDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month within which payment must be received to qualify for the discount specified by `discountPercentage`.'\n        },\n        discountPercentage: {\n          type: 'string',\n          description: 'The discount percentage applied to the payment if received on or before the specified `discountDayOfMonth`. The value is between 0 and 100.'\n        },\n        dueDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month when full payment is due without discount.'\n        },\n        gracePeriodDays: {\n          type: 'number',\n          description: 'The number of days before `dueDayOfMonth` when an invoice or bill issued within this threshold is considered due the following month. For example, with `dueDayOfMonth` set to 15 and `gracePeriodDays` set to 2, an invoice issued on the 13th would be due on the 15th of the next month, while an invoice issued on the 12th would be due on the 15th of the current month.'\n        },\n        isActive: {\n          type: 'boolean',\n          description: 'Indicates whether this date-driven term is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`.'\n        },\n        name: {\n          type: 'string',\n          description: 'The case-insensitive unique name of this date-driven term, unique across all date-driven terms.\\n\\n**NOTE**: Date-driven terms do not have a `fullName` field because they are not hierarchical objects, which is why `name` is unique for them but not for objects that have parents.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_date_driven_term\"`.',\n          enum: [            'qbd_date_driven_term'\n          ]\n        },\n        revisionNumber: {\n          type: 'string',\n          description: 'The current QuickBooks-assigned revision number of this date-driven term object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you\\'re working with the latest data; otherwise, the update will return an error.'\n        },\n        updatedAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'discountDayOfMonth',\n        'discountPercentage',\n        'dueDayOfMonth',\n        'gracePeriodDays',\n        'isActive',\n        'name',\n        'objectType',\n        'revisionNumber',\n        'updatedAt'\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\nCreates a new date-driven term.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/date_driven_term',\n  $defs: {\n    date_driven_term: {\n      type: 'object',\n      title: 'The Date-Driven Term object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this date-driven term. This ID is unique across all date-driven terms but not across different QuickBooks object types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        },\n        discountDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month within which payment must be received to qualify for the discount specified by `discountPercentage`.'\n        },\n        discountPercentage: {\n          type: 'string',\n          description: 'The discount percentage applied to the payment if received on or before the specified `discountDayOfMonth`. The value is between 0 and 100.'\n        },\n        dueDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month when full payment is due without discount.'\n        },\n        gracePeriodDays: {\n          type: 'number',\n          description: 'The number of days before `dueDayOfMonth` when an invoice or bill issued within this threshold is considered due the following month. For example, with `dueDayOfMonth` set to 15 and `gracePeriodDays` set to 2, an invoice issued on the 13th would be due on the 15th of the next month, while an invoice issued on the 12th would be due on the 15th of the current month.'\n        },\n        isActive: {\n          type: 'boolean',\n          description: 'Indicates whether this date-driven term is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`.'\n        },\n        name: {\n          type: 'string',\n          description: 'The case-insensitive unique name of this date-driven term, unique across all date-driven terms.\\n\\n**NOTE**: Date-driven terms do not have a `fullName` field because they are not hierarchical objects, which is why `name` is unique for them but not for objects that have parents.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_date_driven_term\"`.',\n          enum: [            'qbd_date_driven_term'\n          ]\n        },\n        revisionNumber: {\n          type: 'string',\n          description: 'The current QuickBooks-assigned revision number of this date-driven term object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you\\'re working with the latest data; otherwise, the update will return an error.'\n        },\n        updatedAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'discountDayOfMonth',\n        'discountPercentage',\n        'dueDayOfMonth',\n        'gracePeriodDays',\n        'isActive',\n        'name',\n        'objectType',\n        'revisionNumber',\n        'updatedAt'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/qbd/date-driven-terms/list-qbd-date-driven-terms.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_qbd_date_driven_terms',
   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 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.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      description: 'The array of date-driven terms.',\n      items: {\n        $ref: '#/$defs/date_driven_term'\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    date_driven_term: {\n      type: 'object',\n      title: 'The Date-Driven Term object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this date-driven term. This ID is unique across all date-driven terms but not across different QuickBooks object types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        },\n        discountDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month within which payment must be received to qualify for the discount specified by `discountPercentage`.'\n        },\n        discountPercentage: {\n          type: 'string',\n          description: 'The discount percentage applied to the payment if received on or before the specified `discountDayOfMonth`. The value is between 0 and 100.'\n        },\n        dueDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month when full payment is due without discount.'\n        },\n        gracePeriodDays: {\n          type: 'number',\n          description: 'The number of days before `dueDayOfMonth` when an invoice or bill issued within this threshold is considered due the following month. For example, with `dueDayOfMonth` set to 15 and `gracePeriodDays` set to 2, an invoice issued on the 13th would be due on the 15th of the next month, while an invoice issued on the 12th would be due on the 15th of the current month.'\n        },\n        isActive: {\n          type: 'boolean',\n          description: 'Indicates whether this date-driven term is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`.'\n        },\n        name: {\n          type: 'string',\n          description: 'The case-insensitive unique name of this date-driven term, unique across all date-driven terms.\\n\\n**NOTE**: Date-driven terms do not have a `fullName` field because they are not hierarchical objects, which is why `name` is unique for them but not for objects that have parents.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_date_driven_term\"`.',\n          enum: [            'qbd_date_driven_term'\n          ]\n        },\n        revisionNumber: {\n          type: 'string',\n          description: 'The current QuickBooks-assigned revision number of this date-driven term object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you\\'re working with the latest data; otherwise, the update will return an error.'\n        },\n        updatedAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'discountDayOfMonth',\n        'discountPercentage',\n        'dueDayOfMonth',\n        'gracePeriodDays',\n        'isActive',\n        'name',\n        'objectType',\n        'revisionNumber',\n        'updatedAt'\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 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.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      description: 'The array of date-driven terms.',\n      items: {\n        $ref: '#/$defs/date_driven_term'\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    date_driven_term: {\n      type: 'object',\n      title: 'The Date-Driven Term object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this date-driven term. This ID is unique across all date-driven terms but not across different QuickBooks object types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        },\n        discountDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month within which payment must be received to qualify for the discount specified by `discountPercentage`.'\n        },\n        discountPercentage: {\n          type: 'string',\n          description: 'The discount percentage applied to the payment if received on or before the specified `discountDayOfMonth`. The value is between 0 and 100.'\n        },\n        dueDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month when full payment is due without discount.'\n        },\n        gracePeriodDays: {\n          type: 'number',\n          description: 'The number of days before `dueDayOfMonth` when an invoice or bill issued within this threshold is considered due the following month. For example, with `dueDayOfMonth` set to 15 and `gracePeriodDays` set to 2, an invoice issued on the 13th would be due on the 15th of the next month, while an invoice issued on the 12th would be due on the 15th of the current month.'\n        },\n        isActive: {\n          type: 'boolean',\n          description: 'Indicates whether this date-driven term is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`.'\n        },\n        name: {\n          type: 'string',\n          description: 'The case-insensitive unique name of this date-driven term, unique across all date-driven terms.\\n\\n**NOTE**: Date-driven terms do not have a `fullName` field because they are not hierarchical objects, which is why `name` is unique for them but not for objects that have parents.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_date_driven_term\"`.',\n          enum: [            'qbd_date_driven_term'\n          ]\n        },\n        revisionNumber: {\n          type: 'string',\n          description: 'The current QuickBooks-assigned revision number of this date-driven term object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you\\'re working with the latest data; otherwise, the update will return an error.'\n        },\n        updatedAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'discountDayOfMonth',\n        'discountPercentage',\n        'dueDayOfMonth',\n        'gracePeriodDays',\n        'isActive',\n        'name',\n        'objectType',\n        'revisionNumber',\n        'updatedAt'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -80,12 +80,12 @@ export const tool: Tool = {
       updatedAfter: {
         type: 'string',
         description:
-          'Filter for date-driven terms updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for date-driven terms 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 date-driven terms updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for date-driven terms 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.",
       },
       jq_filter: {
         type: 'string',

package/src/tools/qbd/date-driven-terms/retrieve-qbd-date-driven-terms.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'retrieve_qbd_date_driven_terms',
   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\nRetrieves a date-driven term by ID.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/date_driven_term',\n  $defs: {\n    date_driven_term: {\n      type: 'object',\n      title: 'The Date-Driven Term object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this date-driven term. This ID is unique across all date-driven terms but not across different QuickBooks object types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        },\n        discountDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month within which payment must be received to qualify for the discount specified by `discountPercentage`.'\n        },\n        discountPercentage: {\n          type: 'string',\n          description: 'The discount percentage applied to the payment if received on or before the specified `discountDayOfMonth`. The value is between 0 and 100.'\n        },\n        dueDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month when full payment is due without discount.'\n        },\n        gracePeriodDays: {\n          type: 'number',\n          description: 'The number of days before `dueDayOfMonth` when an invoice or bill issued within this threshold is considered due the following month. For example, with `dueDayOfMonth` set to 15 and `gracePeriodDays` set to 2, an invoice issued on the 13th would be due on the 15th of the next month, while an invoice issued on the 12th would be due on the 15th of the current month.'\n        },\n        isActive: {\n          type: 'boolean',\n          description: 'Indicates whether this date-driven term is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`.'\n        },\n        name: {\n          type: 'string',\n          description: 'The case-insensitive unique name of this date-driven term, unique across all date-driven terms.\\n\\n**NOTE**: Date-driven terms do not have a `fullName` field because they are not hierarchical objects, which is why `name` is unique for them but not for objects that have parents.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_date_driven_term\"`.',\n          enum: [            'qbd_date_driven_term'\n          ]\n        },\n        revisionNumber: {\n          type: 'string',\n          description: 'The current QuickBooks-assigned revision number of this date-driven term object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you\\'re working with the latest data; otherwise, the update will return an error.'\n        },\n        updatedAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'discountDayOfMonth',\n        'discountPercentage',\n        'dueDayOfMonth',\n        'gracePeriodDays',\n        'isActive',\n        'name',\n        'objectType',\n        'revisionNumber',\n        'updatedAt'\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\nRetrieves a date-driven term by ID.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/date_driven_term',\n  $defs: {\n    date_driven_term: {\n      type: 'object',\n      title: 'The Date-Driven Term object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this date-driven term. This ID is unique across all date-driven terms but not across different QuickBooks object types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        },\n        discountDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month within which payment must be received to qualify for the discount specified by `discountPercentage`.'\n        },\n        discountPercentage: {\n          type: 'string',\n          description: 'The discount percentage applied to the payment if received on or before the specified `discountDayOfMonth`. The value is between 0 and 100.'\n        },\n        dueDayOfMonth: {\n          type: 'number',\n          description: 'The day of the month when full payment is due without discount.'\n        },\n        gracePeriodDays: {\n          type: 'number',\n          description: 'The number of days before `dueDayOfMonth` when an invoice or bill issued within this threshold is considered due the following month. For example, with `dueDayOfMonth` set to 15 and `gracePeriodDays` set to 2, an invoice issued on the 13th would be due on the 15th of the next month, while an invoice issued on the 12th would be due on the 15th of the current month.'\n        },\n        isActive: {\n          type: 'boolean',\n          description: 'Indicates whether this date-driven term is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`.'\n        },\n        name: {\n          type: 'string',\n          description: 'The case-insensitive unique name of this date-driven term, unique across all date-driven terms.\\n\\n**NOTE**: Date-driven terms do not have a `fullName` field because they are not hierarchical objects, which is why `name` is unique for them but not for objects that have parents.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_date_driven_term\"`.',\n          enum: [            'qbd_date_driven_term'\n          ]\n        },\n        revisionNumber: {\n          type: 'string',\n          description: 'The current QuickBooks-assigned revision number of this date-driven term object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you\\'re working with the latest data; otherwise, the update will return an error.'\n        },\n        updatedAt: {\n          type: 'string',\n          description: 'The date and time when this date-driven term was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'discountDayOfMonth',\n        'discountPercentage',\n        'dueDayOfMonth',\n        'gracePeriodDays',\n        'isActive',\n        'name',\n        'objectType',\n        'revisionNumber',\n        'updatedAt'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/qbd/deleted-list-objects/list-qbd-deleted-list-objects.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_qbd_deleted_list_objects',
   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\nLists deleted non-transaction list-objects (e.g., customers, vendors, employees, items) from the last 90 days. Results are grouped by list-object type and ordered by actual delete time (ascending). For deleted transactions (e.g., invoices, bills, estimates), see the deleted-transactions endpoint.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      description: 'The array of deleted list-objects.',\n      items: {\n        $ref: '#/$defs/deleted_list_object'\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    deleted_list_object: {\n      type: 'object',\n      title: 'The Deleted List-Object object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this deleted list-object. This ID is unique across all deleted list-objects but not across different QuickBooks object types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this deleted list-object was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        },\n        deletedAt: {\n          type: 'string',\n          description: 'The date and time when this deleted list-object was deleted, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        },\n        listType: {\n          type: 'string',\n          description: 'The type of deleted list object (i.e., non-transaction).',\n          enum: [            'account',\n            'billing_rate',\n            'class',\n            'currency',\n            'customer',\n            'customer_message',\n            'customer_type',\n            'date_driven_terms',\n            'employee',\n            'inventory_site',\n            'item_discount',\n            'item_fixed_asset',\n            'item_group',\n            'item_inventory',\n            'item_inventory_assembly',\n            'item_non_inventory',\n            'item_other_charge',\n            'item_payment',\n            'item_sales_tax',\n            'item_sales_tax_group',\n            'item_service',\n            'item_subtotal',\n            'job_type',\n            'other_name',\n            'payment_method',\n            'payroll_item_non_wage',\n            'payroll_item_wage',\n            'price_level',\n            'sales_representative',\n            'sales_tax_code',\n            'ship_method',\n            'standard_terms',\n            'to_do',\n            'unit_of_measure_set',\n            'vehicle',\n            'vendor',\n            'vendor_type',\n            'workers_comp_code'\n          ]\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_deleted_list_object\"`.',\n          enum: [            'qbd_deleted_list_object'\n          ]\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'deletedAt',\n        'listType',\n        'objectType'\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\nLists deleted non-transaction list-objects (e.g., customers, vendors, employees, items) from the last 90 days. Results are grouped by list-object type and ordered by actual delete time (ascending). For deleted transactions (e.g., invoices, bills, estimates), see the deleted-transactions endpoint.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      description: 'The array of deleted list-objects.',\n      items: {\n        $ref: '#/$defs/deleted_list_object'\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    deleted_list_object: {\n      type: 'object',\n      title: 'The Deleted List-Object object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this deleted list-object. This ID is unique across all deleted list-objects but not across different QuickBooks object types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this deleted list-object was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        },\n        deletedAt: {\n          type: 'string',\n          description: 'The date and time when this deleted list-object was deleted, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        },\n        listType: {\n          type: 'string',\n          description: 'The type of deleted list object (i.e., non-transaction).',\n          enum: [            'account',\n            'billing_rate',\n            'class',\n            'currency',\n            'customer',\n            'customer_message',\n            'customer_type',\n            'date_driven_terms',\n            'employee',\n            'inventory_site',\n            'item_discount',\n            'item_fixed_asset',\n            'item_group',\n            'item_inventory',\n            'item_inventory_assembly',\n            'item_non_inventory',\n            'item_other_charge',\n            'item_payment',\n            'item_sales_tax',\n            'item_sales_tax_group',\n            'item_service',\n            'item_subtotal',\n            'job_type',\n            'other_name',\n            'payment_method',\n            'payroll_item_non_wage',\n            'payroll_item_wage',\n            'price_level',\n            'sales_representative',\n            'sales_tax_code',\n            'ship_method',\n            'standard_terms',\n            'to_do',\n            'unit_of_measure_set',\n            'vehicle',\n            'vendor',\n            'vendor_type',\n            'workers_comp_code'\n          ]\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_deleted_list_object\"`.',\n          enum: [            'qbd_deleted_list_object'\n          ]\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'deletedAt',\n        'listType',\n        'objectType'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -76,12 +76,12 @@ export const tool: Tool = {
       deletedAfter: {
         type: 'string',
         description:
-          'Filter for deleted list-objects deleted on or after this date and time, within the last 90 days (QuickBooks limit), in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for deleted list-objects deleted on or after this date/time, within the last 90 days (QuickBooks limit). 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.",
       },
       deletedBefore: {
         type: 'string',
         description:
-          'Filter for deleted list-objects deleted on or before this date and time, within the last 90 days (QuickBooks limit), in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for deleted list-objects deleted on or before this date/time, within the last 90 days (QuickBooks limit). 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.",
       },
       jq_filter: {
         type: 'string',

package/src/tools/qbd/deleted-transactions/list-qbd-deleted-transactions.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_qbd_deleted_transactions',
   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\nLists deleted transactions of the specified type(s) (e.g., invoice, bill, estimate) in the last 90 days. Results are grouped by transaction type and ordered by actual delete time (ascending). NOTE: For deleted non-transaction list-objects (e.g., customer, vendor, employee), see the deleted-list-objects endpoint.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      description: 'The array of deleted transactions.',\n      items: {\n        $ref: '#/$defs/deleted_transaction'\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    deleted_transaction: {\n      type: 'object',\n      title: 'The Deleted Transaction object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this deleted transaction. This ID is unique across all transaction types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this deleted transaction was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        },\n        deletedAt: {\n          type: 'string',\n          description: 'The date and time when this deleted transaction was deleted, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_deleted_transaction\"`.',\n          enum: [            'qbd_deleted_transaction'\n          ]\n        },\n        refNumber: {\n          type: 'string',\n          description: 'The case-sensitive user-defined reference number for this deleted transaction, 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.'\n        },\n        transactionType: {\n          type: 'string',\n          description: 'The type of deleted transaction.',\n          enum: [            'ar_refund_credit_card',\n            'bill',\n            'bill_payment_check',\n            'bill_payment_credit_card',\n            'build_assembly',\n            'charge',\n            'check',\n            'credit_card_charge',\n            'credit_card_credit',\n            'credit_memo',\n            'deposit',\n            'estimate',\n            'inventory_adjustment',\n            'invoice',\n            'item_receipt',\n            'journal_entry',\n            'purchase_order',\n            'receive_payment',\n            'sales_order',\n            'sales_receipt',\n            'sales_tax_payment_check',\n            'time_tracking',\n            'transfer_inventory',\n            'vehicle_mileage',\n            'vendor_credit'\n          ]\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'deletedAt',\n        'objectType',\n        'refNumber',\n        'transactionType'\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\nLists deleted transactions of the specified type(s) (e.g., invoice, bill, estimate) in the last 90 days. Results are grouped by transaction type and ordered by actual delete time (ascending). NOTE: For deleted non-transaction list-objects (e.g., customer, vendor, employee), see the deleted-list-objects endpoint.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      description: 'The array of deleted transactions.',\n      items: {\n        $ref: '#/$defs/deleted_transaction'\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    deleted_transaction: {\n      type: 'object',\n      title: 'The Deleted Transaction object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this deleted transaction. This ID is unique across all transaction types.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this deleted transaction was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        },\n        deletedAt: {\n          type: 'string',\n          description: 'The date and time when this deleted transaction was deleted, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_deleted_transaction\"`.',\n          enum: [            'qbd_deleted_transaction'\n          ]\n        },\n        refNumber: {\n          type: 'string',\n          description: 'The case-sensitive user-defined reference number for this deleted transaction, 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.'\n        },\n        transactionType: {\n          type: 'string',\n          description: 'The type of deleted transaction.',\n          enum: [            'ar_refund_credit_card',\n            'bill',\n            'bill_payment_check',\n            'bill_payment_credit_card',\n            'build_assembly',\n            'charge',\n            'check',\n            'credit_card_charge',\n            'credit_card_credit',\n            'credit_memo',\n            'deposit',\n            'estimate',\n            'inventory_adjustment',\n            'invoice',\n            'item_receipt',\n            'journal_entry',\n            'purchase_order',\n            'receive_payment',\n            'sales_order',\n            'sales_receipt',\n            'sales_tax_payment_check',\n            'time_tracking',\n            'transfer_inventory',\n            'vehicle_mileage',\n            'vendor_credit'\n          ]\n        }\n      },\n      required: [        'id',\n        'createdAt',\n        'deletedAt',\n        'objectType',\n        'refNumber',\n        'transactionType'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -63,12 +63,12 @@ export const tool: Tool = {
       deletedAfter: {
         type: 'string',
         description:
-          'Filter for deleted transactions deleted on or after this date and time, within the last 90 days (QuickBooks limit), in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for deleted transactions deleted on or after this date/time, within the last 90 days (QuickBooks limit). 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.",
       },
       deletedBefore: {
         type: 'string',
         description:
-          'Filter for deleted transactions deleted on or before this date and time, within the last 90 days (QuickBooks limit), in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for deleted transactions deleted on or before this date/time, within the last 90 days (QuickBooks limit). 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.",
       },
       jq_filter: {
         type: 'string',

package/src/tools/qbd/discount-items/list-qbd-discount-items.ts

@@ -92,12 +92,12 @@ export const tool: Tool = {
       updatedAfter: {
         type: 'string',
         description:
-          'Filter for discount items updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for discount items 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 discount items updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for discount items 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.",
       },
     },
     required: ['conductorEndUserId'],

package/src/tools/qbd/employees/list-qbd-employees.ts

@@ -78,12 +78,12 @@ export const tool: Tool = {
       updatedAfter: {
         type: 'string',
         description:
-          'Filter for employees updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for employees 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 employees updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for employees 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.",
       },
     },
     required: ['conductorEndUserId'],

package/src/tools/qbd/estimates/list-qbd-estimates.ts

@@ -108,24 +108,24 @@ export const tool: Tool = {
       transactionDateFrom: {
         type: 'string',
         description:
-          'Filter for estimates whose `date` field is on or after this date, in ISO 8601 format (YYYY-MM-DD).',
+          "Filter for estimates 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 estimates whose `date` field is on or before this date, in ISO 8601 format (YYYY-MM-DD).',
+          "Filter for estimates 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 estimates updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for estimates 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 estimates updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for estimates 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.",
       },
     },
     required: ['conductorEndUserId'],

package/src/tools/qbd/inventory-adjustments/list-qbd-inventory-adjustments.ts

@@ -99,24 +99,24 @@ export const tool: Tool = {
       transactionDateFrom: {
         type: 'string',
         description:
-          'Filter for inventory adjustments whose `date` field is on or after this date, in ISO 8601 format (YYYY-MM-DD).',
+          "Filter for inventory adjustments 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 inventory adjustments whose `date` field is on or before this date, in ISO 8601 format (YYYY-MM-DD).',
+          "Filter for inventory adjustments 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 inventory adjustments updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.',
+          "Filter for inventory adjustments 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 inventory adjustments updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.',
+          "Filter for inventory adjustments 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.",
       },
     },
     required: ['conductorEndUserId'],

package/src/tools/qbd/inventory-assembly-items/list-qbd-inventory-assembly-items.ts

@@ -92,12 +92,12 @@ export const tool: Tool = {
       updatedAfter: {
         type: 'string',
         description:
-          'Filter for inventory assembly items updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.\n\n**WARNING**: Due to a known issue in QuickBooks Desktop, the `updatedAfter` parameter may not correctly filter inventory assembly items by their updated dates. To accurately retrieve the desired inventory assembly items, we recommend avoiding this parameter and instead fetching a broader dataset, then filtering the results locally using the `updatedAt` property.',
+          "Filter for inventory assembly items 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 inventory assembly items updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.\n\n**WARNING**: Due to a known issue in QuickBooks Desktop, the `updatedBefore` parameter may not correctly filter inventory assembly items by their updated dates. To accurately retrieve the desired inventory assembly items, we recommend avoiding this parameter and instead fetching a broader dataset, then filtering the results locally using the `updatedAt` property.',
+          "Filter for inventory assembly items 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.",
       },
     },
     required: ['conductorEndUserId'],

package/src/tools/qbd/inventory-items/list-qbd-inventory-items.ts

@@ -92,12 +92,12 @@ export const tool: Tool = {
       updatedAfter: {
         type: 'string',
         description:
-          'Filter for inventory items updated on or after this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 00:00:00 of that day.\n\n**WARNING**: Due to a known issue in QuickBooks Desktop, the `updatedAfter` parameter may not correctly filter inventory items by their updated dates. To accurately retrieve the desired inventory items, we recommend avoiding this parameter and instead fetching a broader dataset, then filtering the results locally using the `updatedAt` property.',
+          "Filter for inventory items 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 inventory items updated on or before this date and time, in ISO 8601 format (YYYY-MM-DDTHH:mm:ss). If you only provide a date (YYYY-MM-DD), the time is assumed to be 23:59:59 of that day.\n\n**WARNING**: Due to a known issue in QuickBooks Desktop, the `updatedBefore` parameter may not correctly filter inventory items by their updated dates. To accurately retrieve the desired inventory items, we recommend avoiding this parameter and instead fetching a broader dataset, then filtering the results locally using the `updatedAt` property.',
+          "Filter for inventory items 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.",
       },
     },
     required: ['conductorEndUserId'],

package/src/tools/qbd/inventory-sites/create-qbd-inventory-sites.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'create_qbd_inventory_sites',
   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\nCreates a new inventory site.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/inventory_site',\n  $defs: {\n    inventory_site: {\n      type: 'object',\n      title: 'The Inventory Site object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this inventory site. This ID is unique across all inventory sites but not across different QuickBooks object types.'\n        },\n        address: {\n          type: 'object',\n          title: 'The Site Address object',\n          description: 'The inventory site\\'s address.',\n          properties: {\n            city: {\n              type: 'string',\n              description: 'The city, district, suburb, town, or village name of the site address.'\n            },\n            country: {\n              type: 'string',\n              description: 'The country name of the site address.'\n            },\n            line1: {\n              type: 'string',\n              description: 'The first line of the site address (e.g., street, PO Box, or company name).'\n            },\n            line2: {\n              type: 'string',\n              description: 'The second line of the site address, if needed (e.g., apartment, suite, unit, or building).'\n            },\n            line3: {\n              type: 'string',\n              description: 'The third line of the site address, if needed.'\n            },\n            line4: {\n              type: 'string',\n              description: 'The fourth line of the site address, if needed.'\n            },\n            line5: {\n              type: 'string',\n              description: 'The fifth line of the site address, if needed.'\n            },\n            postalCode: {\n              type: 'string',\n              description: 'The postal code or ZIP code of the site address.'\n            },\n            state: {\n              type: 'string',\n              description: 'The state, county, province, or region name of the site address.'\n            }\n          },\n          required: [            'city',\n            'country',\n            'line1',\n            'line2',\n            'line3',\n            'line4',\n            'line5',\n            'postalCode',\n            'state'\n          ]\n        },\n        contact: {\n          type: 'string',\n          description: 'The name of the primary contact person for this inventory site.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this inventory site was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        },\n        description: {\n          type: 'string',\n          description: 'A description of this inventory site.'\n        },\n        email: {\n          type: 'string',\n          description: 'The inventory site\\'s email address.'\n        },\n        fax: {\n          type: 'string',\n          description: 'The inventory site\\'s fax number.'\n        },\n        isActive: {\n          type: 'boolean',\n          description: 'Indicates whether this inventory site is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`.'\n        },\n        isDefault: {\n          type: 'boolean',\n          description: 'Indicates whether this inventory site is the default site used when no specific site is provided during the creation of other objects.'\n        },\n        name: {\n          type: 'string',\n          description: 'The case-insensitive unique name of this inventory site, unique across all inventory sites.\\n\\n**NOTE**: Inventory sites do not have a `fullName` field because they are not hierarchical objects, which is why `name` is unique for them but not for objects that have parents.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_inventory_site\"`.',\n          enum: [            'qbd_inventory_site'\n          ]\n        },\n        parent: {\n          type: 'object',\n          description: 'The parent inventory site one level above this one in the hierarchy.',\n          properties: {\n            id: {\n              type: 'string',\n              description: 'The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types.'\n            },\n            fullName: {\n              type: 'string',\n              description: 'The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive.'\n            }\n          },\n          required: [            'id',\n            'fullName'\n          ]\n        },\n        phone: {\n          type: 'string',\n          description: 'The inventory site\\'s primary telephone number.'\n        },\n        revisionNumber: {\n          type: 'string',\n          description: 'The current QuickBooks-assigned revision number of this inventory site object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you\\'re working with the latest data; otherwise, the update will return an error.'\n        },\n        updatedAt: {\n          type: 'string',\n          description: 'The date and time when this inventory site was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm). The time zone is the same as the user\\'s time zone in QuickBooks.'\n        }\n      },\n      required: [        'id',\n        'address',\n        'contact',\n        'createdAt',\n        'description',\n        'email',\n        'fax',\n        'isActive',\n        'isDefault',\n        'name',\n        'objectType',\n        'parent',\n        'phone',\n        'revisionNumber',\n        'updatedAt'\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\nCreates a new inventory site.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/inventory_site',\n  $defs: {\n    inventory_site: {\n      type: 'object',\n      title: 'The Inventory Site object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The unique identifier assigned by QuickBooks to this inventory site. This ID is unique across all inventory sites but not across different QuickBooks object types.'\n        },\n        address: {\n          type: 'object',\n          title: 'The Site Address object',\n          description: 'The inventory site\\'s address.',\n          properties: {\n            city: {\n              type: 'string',\n              description: 'The city, district, suburb, town, or village name of the site address.'\n            },\n            country: {\n              type: 'string',\n              description: 'The country name of the site address.'\n            },\n            line1: {\n              type: 'string',\n              description: 'The first line of the site address (e.g., street, PO Box, or company name).'\n            },\n            line2: {\n              type: 'string',\n              description: 'The second line of the site address, if needed (e.g., apartment, suite, unit, or building).'\n            },\n            line3: {\n              type: 'string',\n              description: 'The third line of the site address, if needed.'\n            },\n            line4: {\n              type: 'string',\n              description: 'The fourth line of the site address, if needed.'\n            },\n            line5: {\n              type: 'string',\n              description: 'The fifth line of the site address, if needed.'\n            },\n            postalCode: {\n              type: 'string',\n              description: 'The postal code or ZIP code of the site address.'\n            },\n            state: {\n              type: 'string',\n              description: 'The state, county, province, or region name of the site address.'\n            }\n          },\n          required: [            'city',\n            'country',\n            'line1',\n            'line2',\n            'line3',\n            'line4',\n            'line5',\n            'postalCode',\n            'state'\n          ]\n        },\n        contact: {\n          type: 'string',\n          description: 'The name of the primary contact person for this inventory site.'\n        },\n        createdAt: {\n          type: 'string',\n          description: 'The date and time when this inventory site was created, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        },\n        description: {\n          type: 'string',\n          description: 'A description of this inventory site.'\n        },\n        email: {\n          type: 'string',\n          description: 'The inventory site\\'s email address.'\n        },\n        fax: {\n          type: 'string',\n          description: 'The inventory site\\'s fax number.'\n        },\n        isActive: {\n          type: 'boolean',\n          description: 'Indicates whether this inventory site is active. Inactive objects are typically hidden from views and reports in QuickBooks. Defaults to `true`.'\n        },\n        isDefault: {\n          type: 'boolean',\n          description: 'Indicates whether this inventory site is the default site used when no specific site is provided during the creation of other objects.'\n        },\n        name: {\n          type: 'string',\n          description: 'The case-insensitive unique name of this inventory site, unique across all inventory sites.\\n\\n**NOTE**: Inventory sites do not have a `fullName` field because they are not hierarchical objects, which is why `name` is unique for them but not for objects that have parents.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_inventory_site\"`.',\n          enum: [            'qbd_inventory_site'\n          ]\n        },\n        parent: {\n          type: 'object',\n          description: 'The parent inventory site one level above this one in the hierarchy.',\n          properties: {\n            id: {\n              type: 'string',\n              description: 'The unique identifier assigned by QuickBooks to this object. This ID is unique across all objects of the same type, but not across different QuickBooks object types.'\n            },\n            fullName: {\n              type: 'string',\n              description: 'The fully-qualified unique name for this object, formed by combining the names of its parent objects with its own `name`, separated by colons. Not case-sensitive.'\n            }\n          },\n          required: [            'id',\n            'fullName'\n          ]\n        },\n        phone: {\n          type: 'string',\n          description: 'The inventory site\\'s primary telephone number.'\n        },\n        revisionNumber: {\n          type: 'string',\n          description: 'The current QuickBooks-assigned revision number of this inventory site object, which changes each time the object is modified. When updating this object, you must provide the most recent `revisionNumber` to ensure you\\'re working with the latest data; otherwise, the update will return an error.'\n        },\n        updatedAt: {\n          type: 'string',\n          description: 'The date and time when this inventory site was last updated, in ISO 8601 format (YYYY-MM-DDThh:mm:ss±hh:mm), which QuickBooks Desktop interprets in the local timezone of the end-user\\'s computer.'\n        }\n      },\n      required: [        'id',\n        'address',\n        'contact',\n        'createdAt',\n        'description',\n        'email',\n        'fax',\n        'isActive',\n        'isDefault',\n        'name',\n        'objectType',\n        'parent',\n        'phone',\n        'revisionNumber',\n        'updatedAt'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {