FFlashpricer
On this page
MCP Integration

Bulk updates: the read tools

The read-only MCP tools for tracking your bulk updates — list recent runs, check progress, and pull the per-row error report — with example prompts.

Published 7/12/2026Updated 7/12/2026
MCP · Reference · Read
Bulk updates: the read tools

After you push a bulk update, a connected AI assistant can track it for you in plain language — see the status, the per-outcome breakdown, and the row-by-row error report. Here are the two read-only Bulk update tools.

2 read tools Read-onlyNever changes your data

Not connected yet? Start with Connect an AI assistant to Flashpricer (MCP). Want to push a bulk update? See Bulk updates: the write tool.

i

Read-only, scoped to you. These tools only report on bulk updates — they change nothing. They use the Products · view permission and only ever see your organization's data.

Track your bulk updates

list-bulk-updatesReadproducts · view

Lists your recent bulk updates with, for each one, its status, file name, total items and a per-outcome breakdown — not found, invalid value, no change, price changes, failed — plus whether an error report is available.

Options: days (how far back, default 30, max 30).
Ask"Show me my recent bulk updates and how they went."
get-bulk-updateReadproducts · view

Gets one bulk update by id — its status, progress, total items, and (when ready) a short-lived link to its error report CSV with the per-row outcome (not found, invalid, applied). The assistant can read that report to explain what went wrong.

Needs: a requestId (from list-bulk-updates or from create-bulk-update). If it's still running, the assistant polls until it's done.
Ask"Did my last bulk update apply cleanly? Show me the errors."

Tips for better answers

  • Just describe it. You never need ids — say "how did my last bulk update go?" and the assistant finds it and reads the report.
  • Ask it to explain failures. The error report is fetchable, so the assistant can open it and tell you exactly which rows didn't apply and why ("which SKUs weren't found?").
  • Poll patiently. Large updates run in the background — the assistant checks back until the status is complete.
Ready to check a run?

Open your connected assistant and ask "How did my last bulk update go, and were there any errors?" To push a bulk update, see the write tool. Questions? Reach us at success@flashpricer.com.

Was this article helpful?
Bulk updates: the read MCP tools | Flashpricer · Flashpricer