store/list-order-notes reads the notes recorded against an order: both the internal ones and those sent to the customer, with who added each and when.
WooCommerce can add a note and has no way to read one back. That gap is why this exists.
At a glance
| Ability | store/list-order-notes |
| Toolset | WooCommerce — toolset/woocommerce |
| Group | WooCommerce › Orders & Refunds |
| Requires | WooCommerce, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Order notes are where the history of an order lives. Gateway responses, status changes, staff comments about a delivery problem, the message sent to the customer when something was delayed — all of it, in one thread, and none of it readable through any standard route.
Which makes this the call to run before doing anything about an order. “The customer says they never got a refund” is a completely different situation depending on whether a note from three days ago says a refund was issued in the gateway.
The notes distinguish internal from customer-facing. A customer-facing note was emailed; an internal one was not, and assuming otherwise is how a customer gets told something twice or not at all.
The author is recorded, including when the author was WooCommerce itself rather than a person.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | Order ID. |
limit | integer | No | How many notes to return. |
What comes back
| Name | Type | What it is |
|---|---|---|
order_id | integer | The order. |
notes | array | One entry per note: the text, whether it was sent to the customer, the author and the date. |
count | integer | How many notes were returned. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
What has already been done about order 4471?
It resolves to one call:
{
"ability": "store/list-order-notes",
"parameters": {
"id": 4471
}
}Worth knowing
- Read this before acting on an order. It is the history nothing else exposes.
- Customer-facing notes were emailed; internal ones were not.
- System notes record gateway responses and status changes.
Related abilities
- Get Order — the order itself
- Refund an Order — which adds a note of its own
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category