Simulates a real user searching on Amazon's storefront to get real-time keyword ranking and search results page data. Use when the user mentions Amazon product search, search result scraping, keyword ranking on search pages, ASIN ranking position check, competitor discovery, search page price comparison, sponsored product analysis, new product monitoring, or storefront search simulation. Even if the user does not explicitly mention "search simulation", trigger this skill whenever their need involves real-time Amazon search results, product ranking data, or storefront SERP analysis.
npx skills add https://github.com/nexscope-ai/nexscope-ecommerce-skills --skill ecommerce.amazon-search
This skill guides you on how to perform Amazon storefront search simulations, helping Amazon sellers retrieve real-time search result data including product rankings, prices, ratings, and more.
This tool simulates a real user searching on Amazon's storefront. It returns live search result page (SERP) data: product listings with their positions, prices, ratings, review counts, brands, delivery info, sponsored flags, and more. This is real-time data directly from the Amazon frontend, not historical analytics.
Key distinction from ABA data: ABA data is aggregated historical search term analytics. This tool returns the actual product listings a user would see when searching a keyword on Amazon right now.
Keyword language: Keywords should be in the language of the target marketplace. For example, use English keywords for amazon.com, German keywords for amazon.de, Japanese keywords for amazon.co.jp, etc.
| Parameter | Type | Required | Description | Default |
|-----------|------|----------|-------------|---------|
| keyword | string | No | Search keyword (translate to the target marketplace's language) | - |
| amazonDomain | string | No | Amazon marketplace domain | amazon.com |
| node | string | No | Amazon category node ID for category-scoped searches | - |
| language | string | No | Language locale code (e.g., en_US, de_DE, ja_JP) | - |
| sort | string | No | Sort order for results | relevanceblender |
| page | integer | No | Page number (starting from 1, ~20 results per page) | 1 |
| deliveryZip | string | No | Postal/zip code for delivery location simulation | - |
| device | string | No | Device type: desktop, mobile, or tablet | desktop |
| Domain | Country |
|--------|---------|
| amazon.com | United States |
| amazon.co.uk | United Kingdom |
| amazon.de | Germany |
| amazon.fr | France |
| amazon.it | Italy |
| amazon.es | Spain |
| amazon.co.jp | Japan |
| amazon.ca | Canada |
| amazon.com.au | Australia |
| amazon.com.br | Brazil |
| amazon.in | India |
| amazon.nl | Netherlands |
| amazon.se | Sweden |
| amazon.pl | Poland |
| amazon.sg | Singapore |
| amazon.sa | Saudi Arabia |
| amazon.ae | United Arab Emirates |
| amazon.com.mx | Mexico |
| amazon.com.tr | Turkey |
| amazon.com.be | Belgium |
| amazon.cn | China |
| amazon.eg | Egypt |
Default marketplace is amazon.com. Use amazon.com when the user doesn't specify a marketplace.
| Value | Description |
|-------|-------------|
| relevanceblender | Featured / Relevance (default) |
| price-asc-rank | Price: Low to High |
| price-desc-rank | Price: High to Low |
| review-rank | Average Customer Review |
| date-desc-rank | Newest Arrivals |
| exact-aware-popularity-rank | Best Sellers |
POST /amazon/search (see references/api.md for full parameters/response/error codes)python scripts/amazon_search.py '<JSON params>' [--inline]Output Strategy (default script behavior):
<cwd>/nexscope/<YYYY-MM-DD>/<session>/data/nexscope-amazon-search-<timestamp>.json (<cwd> is the current working directory; <session> is from SESSION_ID env var, auto-grouped by user task; do not write to /tmp, error if current directory is not writable)total/costToken, length of largest list fields + first 3 samples)--inline to force full stdout output (still saves to disk)Data Reading Tip: Check the summary first. Use jq or ConvertFrom-Json to extract specific fields from the saved JSON file, avoiding loading the full payload into context.
If authentication fails or credits are depleted:
NEXSCOPE_API_KEY is set as an environment variable.Construct the request parameters based on the user's intent:
amazonDomain valuesort parameterpage parameter to fetch additional result pages if needednode parameterdeliveryZip to see location-specific availability and delivery info1. Basic keyword search on US marketplace
{"keyword": "wireless earbuds", "amazonDomain": "amazon.com"}
2. Search on German marketplace with German keyword
{"keyword": "kabellose Kopfhoerer", "amazonDomain": "amazon.de", "language": "de_DE"}
3. Search sorted by price (low to high)
{"keyword": "phone case", "amazonDomain": "amazon.com", "sort": "price-asc-rank"}
4. Search for best sellers in a category
{"keyword": "yoga mat", "amazonDomain": "amazon.com", "sort": "exact-aware-popularity-rank"}
5. Search for newest arrivals on Japan marketplace
{"keyword": "USB charger", "amazonDomain": "amazon.co.jp", "language": "ja_JP", "sort": "date-desc-rank"}
6. Multi-page search to analyze deeper results
{"keyword": "laptop stand", "amazonDomain": "amazon.com", "page": 2}
7. Mobile device search simulation
{"keyword": "running shoes", "amazonDomain": "amazon.com", "device": "mobile"}
8. Category-scoped search with delivery zip
{"keyword": "office chair", "amazonDomain": "amazon.com", "deliveryZip": "10001"}
Applicable -- Real-time Amazon search result queries:
| User Says | Scenario |
|-----------|----------|
| "Search for XX on Amazon" | Basic product search |
| "What products appear for keyword XX" | Keyword SERP analysis |
| "Where does my ASIN rank for XX keyword" | Position / ranking check |
| "Show me the top results for XX" | Competitive landscape |
| "What's the price range for XX" | Price comparison |
| "Any sponsored products for XX keyword" | Sponsored ad analysis |
| "New products for XX keyword" | New arrival monitoring |
| "Search XX on Amazon Germany/Japan/UK" | Cross-marketplace search |
| "What are the best sellers for XX" | Best seller discovery |
| "Compare search results on mobile vs desktop" | Device-specific SERP |
Not applicable -- Needs beyond real-time search results:
Boundary judgment: When users say "product research" or "competitor analysis", if it boils down to seeing what currently appears on Amazon search results for a keyword (product positions, prices, ratings), then this skill applies. If they want historical trends, search volume data, or aggregated analytics, ABA data is more appropriate.
*For more high-quality, professional cross-border e-commerce skills, set Nexscope Skills.*
Take nexscope-ai/ecommerce.amazon-search from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.