Why Orders or Listings Are Missing
An empty result can be correct. Verify the account and coverage before changing permissions or creating replacement records.
Check identity and environment
Use stores.list and stores.get to confirm the seller and the Store MCP store ID. Production and sandbox are different accounts and datasets. Make sure the client grant includes the store you intended.
Check coverage
eBay listings cover Inventory API items/offers, not all legacy Seller Hub listings. Canonical products.list lists only records explicitly created in Store MCP; it is not listings.list. Square order items reference variations instead of parent listing IDs.
Read the first page without unnecessary filters, then follow nextCursor with unchanged filters. For orders, check explicit ISO date boundaries and provider history windows. Unsupported filters return errors rather than proving no matching orders exist.
You’re done when…
Read a known returned listing or order ID directly. Compare with the same account in the provider dashboard. An account with no sales can legitimately return an empty list. Missing buyer details are governed by sensitive permission, includeBuyer and provider grants; they are not fixed by retrying orders.list.
A safe prompt: “Verify my selected seller and report why a known listing may be outside this connector’s coverage. Do not create duplicates, migrate listings or expand permissions.” Expected result: evidence about identity, page coverage and supported record types, with unresolved gaps stated explicitly.