StoreMCP
Documentation menu

Find Low-Stock Products with AI

A useful low-stock review defines both the threshold and the stock being counted.

Prerequisites

Connect an available store, authorize the selected store with View only access and verify a known listing or order. Check stores.get for provider capabilities. These are on-demand tasks; Store MCP does not schedule reports.

Steps

  1. Name the stores, locations and a threshold, for example fewer than five sellable units.
  2. Page through listings in the agreed scope, then inventory.get for each selected listing and all its inventory pages.
  3. Group by store, variation and location. Count each quantityPoolId once within its response. Keep untracked/null quantities separate.
  4. Check a sample low-stock row in the provider dashboard before ordering or changing stock.

Safe example

The example uses synthetic names. Select your own authorized store and verify every identifier before a write.

Find quantities below 5 for the selected store and locations. Show listing, SKU, variation and location, distinguish zero from unknown, and report unread pages. Do not adjust stock.

You’re done when…

Expect a bounded list with source store and checked locations, plus a separate unknown-data list. It is incomplete if the client stopped before the last cursor.

Limitations

There is no background low-stock monitor or automatic replenishment. Shared stock pools can appear on several variants; adding every variant row can overcount. Pool identifiers cannot be joined across response types.

Next steps and troubleshooting