linkfox-keepa-product-search（Linkfox Keepa 产品搜索）

Keepa Product Search

This skill guides you on how to search and filter Amazon products using Keepa's extensive product database, helping Amazon sellers find products that match specific criteria across multiple dimensions.

Core Concepts

This tool provides advanced Amazon product search powered by Keepa data. Unlike a simple Amazon storefront search, it supports multi-criteria filtering: category, price range, monthly sales volume, BSR (Best Sellers Rank), keyword matching (positive and negative), review counts, ratings, package dimensions, weight, fulfillment type, historical sales rank, and more. It returns detailed product data including pricing, titles, images, listing dates, materials, weights, monthly sales for the past 12 months, and more.

BSR (Best Sellers Rank): A lower salesRank value means better sales performance. Rank 1 is the best-selling product in its category. When a user says "top-selling products", they want low BSR values.

Price unit: Prices are expressed in the smallest currency unit (e.g., cents for USD). So $25.99 = 2599. Always convert when building queries and when displaying results.

Category names: The categoriesIncludeNames parameter supports multi-level category paths separated by a colon : or the > character. Automatically convert user input into the correct format.

Parameters

Marketplace (Required)

Domain ID mapping:

Default marketplace is 1 (US). Use domain 1 when the user doesn't specify a marketplace.

Keyword Filtering

Category Filtering

Sales & Ranking Filters

Price Filters

Review & Rating Filters

Package & Dimensions Filters

Other Filters

Data Options

Pagination & Sorting

Sortable fields: availableDate, currentSales, monthlySold, currentRating, currentCountReviews, currentBuyBoxShipping, currentNew

API Usage

This tool calls the LinkFox tool gateway API. See references/api.md for calling conventions, request parameters, and response structure. You can also execute scripts/keepa_product_search.py directly to run queries.

How to Build Queries

Construct the request parameters based on the user's intent:

1. Determine the marketplace: Map the user's target country to the correct domain ID value
2. Set keyword filters: Use keyword for title-based filtering with positive and negative terms
3. Set category scope: Use categoriesIncludeNames or rootCategoryNames to scope by category; convert user input into proper category path format
4. Apply numeric filters: Map sales volume, price, BSR, review, and rating requirements to the appropriate Gte/Lte parameters
5. Set sort order: If the user wants results sorted by sales, price, or rating, configure the sort array
6. Enable historical data: Set history to 1 if the user needs monthly sales trends or price history

Usage Examples

1. Search for electronics with monthly sales over 1000 on US marketplace

{"domain": "1", "rootCategoryNames": ["Electronics"], "monthlySoldGte": 1000}

2. Find products in a price range with good ratings

{"domain": "1", "currentBuyBoxShippingGte": 1500, "currentBuyBoxShippingLte": 5000, "currentRatingGte": 4.0, "keyword": "wireless charger"}

3. New products listed in the last 6 months with low review counts

{"domain": "1", "availableDateGte": "2025-10-01", "currentCountReviewsLte": 50, "monthlySoldGte": 500}

4. BSR rank filtering for competitive analysis

{"domain": "1", "categoriesIncludeNames": ["Home & Kitchen"], "currentSalesLte": 5000, "sort": [{"fieldName": "monthlySold", "sortDirection": "desc"}]}

5. Find non-Amazon FBA products with good sales

{"domain": "1", "buyBoxIsAmazon": false, "buyBoxIsFBA": true, "monthlySoldGte": 300, "currentRatingGte": 4.0}

6. Lightweight small products for easy shipping

{"domain": "1", "packageWeightLte": 500, "packageLengthLte": 200, "packageWidthLte": 150, "packageHeightLte": 100, "monthlySoldGte": 200}

7. Search on Japan marketplace with historical data

{"domain": "5", "keyword": "USB charger", "history": 1, "monthlySoldGte": 100}

8. Brand-specific search excluding hazardous materials

{"domain": "1", "brand": ["Anker", "UGREEN"], "isHazMat": false, "sort": [{"fieldName": "monthlySold", "sortDirection": "desc"}]}

Display Rules

1. Present data clearly: Show search results in well-structured tables with key fields: ASIN, title, price, BSR, monthly sales, rating, review count, brand
2. Price conversion: Convert prices from smallest currency unit to standard format (e.g., 2599 -> $25.99)
3. BSR clarification: When showing BSR data, remind users that lower values mean better sales ranking
4. Monthly sales history: When historical data is included, present the 12-month sales trend clearly
5. Pagination notice: Inform users of the total result count and suggest fetching additional pages if needed
6. Image links: If image URLs are available, mention them but do not attempt to render them inline unless the user requests it
7. Error handling: When a query fails, explain the reason and suggest adjusting filter criteria

Important Limitations

• Result cap: Maximum 100 results per page, minimum 50
• Sort limit: Maximum 3 sort rules per query
• Category limit: Maximum 50 category IDs or names per filter
• Keyword limit: Maximum 50 keywords in keyword parameter
• Historical data cost: Setting history=1 increases response size and token cost significantly
• Price unit: All price values are in the smallest currency unit (cents, pence, etc.)

User Expression & Scenario Quick Reference

Applicable -- Multi-criteria Amazon product search and filtering:

Not applicable -- Needs beyond product search:

• Real-time Amazon search result page simulation (use Amazon Search)
• Historical search term volume or ranking trends (use ABA data)
• Product review content or sentiment analysis
• Advertising campaign management or bid optimization
• Listing optimization or copywriting suggestions
• Inventory or supply chain data

Boundary judgment: When users say "product research" or "find products", if it involves filtering by sales metrics, BSR, price, category, and other structured criteria, this skill applies. If they want to see what appears on the actual Amazon search page for a keyword, use Amazon Search instead. If they want search term analytics, use ABA data.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

1. The functionality or purpose described in this skill does not match actual behavior
2. The skill's results do not match the user's intent
3. The user expresses dissatisfaction or praise about this skill
4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

*For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.*