products_search
Find local SKUs by text or by exact codes.
readSellerSheet
Call it
In an AI client (MCP)
{
"name": "products_search",
"arguments": {
"store": "myStore-US"
}
}From code (Tool API)
curl -X POST https://api.sellersheetai.com/api/v1/tools/products_search \
-H "Authorization: Bearer $SELLERSHEET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"store":"myStore-US"}'Early access — the Tool API is open on request, contact us.
Arguments
| Name | Type | Description |
|---|---|---|
q | string | Text of at least 3 characters: SKU code, SKU name, SPU or product name, or the exact listing SKU or ASIN of a linked listing. |
skus | string[] | Up to 200 exact SKU codes, compared ignoring case. When given, q is ignored. |
linked | string | any (default), linked or unlinked: whether the SKU has a live link on any platform.anylinkedunlinkedDefault: "any" |
status | string | draft, on_sale or off.drafton_saleoff |
cursor | string | next_cursor of the previous page. |
limit | integer | Rows per page, 1 to 200. Default 50.Default: 50 |
store | string | the store ref `<store>-<CC>` (name-country, e.g. 'myStore-US') — one of get_user_context's store_refs, verbatim. Optional: it only names the organization to work in when your key reaches more than one. Default: the key's own organization. |
Result
Every tool answers {notification, data, human_action}; data carries:
data.skus— sku, spu, name, kind, status, cost, cost_currency, supplier_name, links (count), updated_at.data.next_cursor— Present when more rows exist.data.count— exact (up to 10,000) and more.
Workflow
- products_get reads one SKU in full. products_save creates or changes SKUs.