get_product_changes
Recent catalogue edits — price changes, stock going to zero or coming back, status changes and new products.
When to use it
To explain a behavioural change with a catalogue cause: "bounce rate spiked the same day the price doubled". It is also where you get change dates for get_before_after, instead of asking the merchant when something shipped.
Ask for it like this
You do not name the tool. These are questions that make an assistant reach for it:
What changed in my catalogue last week?
When did I last change prices?
How to read the result
- Recorded from both the nightly sync and the product webhooks, so a change is logged within seconds of happening.
Parameters
changeType
Restrict to price_change, stock_change, status_change or new_product.
productId
Restrict to one product.
limit
Maximum changes to return.
Shared parameters it accepts
Documented in full on the tool reference index.
Date window — defaults to the last 30 days.
dateFrom
Start of the window, YYYY-MM-DD. Inclusive.
dateTo
End of the window, YYYY-MM-DD. Inclusive.
Every tool also accepts merchantId, which resolves from your connection. You never pass it.
What comes back
JSON. These are the top-level keys; date-scoped tools additionally carry a _meta block with the server date and the data coverage envelope.
changes
Per change: product_title, the change type, old and new values, and when it happened.