# products_search (https://sellersheetai.com/docs/mcp-api/tools/products_search)

> Find local SKUs by text or by exact codes.

Access: **READ** · toolset sellersheet · family null

## Call it

MCP tool call:

```json
{
  "name": "products_search",
  "arguments": {}
}
```

Tool API (early access — contact us):

```bash
curl -X POST https://api.sellersheetai.com/api/v1/tools/products_search \
  -H "Authorization: Bearer $SELLERSHEET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'
```

## Arguments

| Name | Type | Required | 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. Allowed: any \| linked \| unlinked. |
| `status` | string |  | draft, on_sale or off. Allowed: draft \| on_sale \| off. |
| `cursor` | string |  | next_cursor of the previous page. |
| `limit` | integer |  | Rows per page, 1 to 200. 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

- `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.