View & search listings
Search your whole catalog, find suppressed or errored listings, and pull everything into a Google Sheet for review — or look up any ASIN on Amazon.
In short
Ask for the listings you care about — by keyword, ASIN, SKU, status or issue — and your agent searches your catalog, explains what is wrong, and can write the list to a sheet for you to work through.
In your daily workflow
Find listings with issues
"Show me every listing that is suppressed or has warnings." listings_searchListingsItems filters your catalog by status and issue severity (ERROR means suppressed) and returns the reasons Amazon gives.
Look closer at one SKU
listings_getListingsItem returns what Amazon has on file for one SKU right now: attributes, offers, status and issues.
Audit in bulk
listings_fetch_attributes_by_skus (your SKUs) and listings_fetch_attributes_by_asins (any ASIN) pull full attribute sets for a batch at once — the starting point for a side-by-side review in your sheet. See Attributes & Publish Queue.
Look up any product on Amazon
catalogItems_searchCatalogItems searches the Amazon catalog by keyword or identifier (ASIN, UPC, EAN); catalogItems_getCatalogItem returns the detail of one ASIN — competitors' included. listings_getListingsRestrictions tells you whether you may sell an ASIN, and in which condition.
Try asking
"Show me all my listings that have issues or are suppressed."
"Write them to a sheet, and show me the suppressed ones first."
Your agent lists each problem with Amazon's reason — a missing main image, a restricted category waiting for approval, a missing description — and writes the rows to the sheet you name.
The search, both ways
The same tool and the same arguments — through your AI client, or from your own code.
MCP — you ask: "Which of my listings are suppressed?" Your agent calls listings_searchListingsItems with an issue filter, pages through the results, and explains each one.
In an AI client (MCP)
{
"name": "listings_searchListingsItems",
"arguments": {
"store": "myStore-US",
"with_issue_severity": [
"ERROR"
],
"included_data": [
"summaries",
"issues"
]
}
}From code (Tool API)
curl -X POST https://api.sellersheetai.com/api/v1/tools/listings_searchListingsItems \
-H "Authorization: Bearer $SELLERSHEET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"store":"myStore-US","with_issue_severity":["ERROR"],"included_data":["summaries","issues"]}'Tools on this page
Pulled from the catalog at build time, each with its own access label.
| Tool | Access | What it does |
|---|---|---|
listings_searchListingsItems | read | Search and filter the seller's own listings catalog — the entry point for a suppressed-listing audit (with_issue_severity ['ERROR'] and included_data ['summaries', 'issues'], then |
listings_getListingsItem | read | Get the SELLER'S SUBMITTED attributes, status, and issues for a single listing SKU. |
listings_fetch_attributes_by_skus | read | Bulk fetch + flatten Amazon listings attributes for N OWNED SKUs in ONE call. |
listings_fetch_attributes_by_asins | read | Bulk fetch + flatten Amazon catalog attributes for N ASINs in ONE call. |
catalogItems_searchCatalogItems | read | Search Amazon's live catalog by keywords or by identifiers — what shoppers see, not one seller's submission. |
catalogItems_getCatalogItem | read | Get Amazon's LIVE catalog data for a single ASIN — the reconciled version that shoppers see on the detail page. |
listings_getListingsRestrictions | read | Check whether you are approved to sell an ASIN in a given condition. |
FAQ
How does my agent get past the first page?
It passes the page token from each result into the next call. See Paging.
Found the problem — how do I fix it?
Edit the attributes in a Publish Queue sheet and submit them — see Attributes & Publish Queue — or ask your agent to change one attribute with a patch (Create listings).