get_js_errors
JavaScript exceptions on the storefront — message, affected pages, frequency, and first and last seen.
When to use it
After any deploy, and whenever conversion drops without an obvious cause. get_conversion_correlations will tell you whether the errors are actually costing money.
Ask for it like this
You do not name the tool. These are questions that make an assistant reach for it:
Are there JavaScript errors on my store?
Is my best revenue running through a known bug?
How to read the result
- Check get_page_dom_snapshot first for TypeError and null-property errors. Many map to an element that exists on some templates and not others.
- Correlate spikes with get_anomalies and get_product_changes to tie an error to a theme or inventory update.
- "Script error." is CORS-stripped and carries no detail. Those need a live browser to diagnose.
Parameters
url
Restrict to pages containing this string.
limit
Maximum distinct errors 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.
errors
Per distinct error: message, affected pages, occurrences, first_seen and last_seen.