This skill queries daily sales estimates and last known price for a given Amazon ASIN via the Jungle Scout data source, returning day-level data points over a specified date range across 10 Amazon marketplaces.
Core Concepts
The Jungle Scout ASIN Sales Estimates tool provides, for a single ASIN on each Amazon marketplace,daily estimated salesandlatest known price. Sellers can query sales changes within a specified time range to:
- Monitor competitor sales: understand competitors' daily order volume and assess their market share
- Validate product selection opportunities: use actual sales data to verify whether product demand is large enough
- Track seasonal patterns: observe sales fluctuations of a product across different months to determine peak and off seasons
- Assess pricing impact: combine the relationship between price and sales changes to assist pricing decisions
- Track new product performance: track the sales ramp-up curve after a new product is listed
Data granularity: each record represents 1 day, including the estimated units sold on that day and the latest known price (USD).
Data Fields
Output Fields
| Field | API Name | Description | Example |
|---|---|---|---|
| ASIN | asin | Queried ASIN | B0CXXX1234 |
| Data identifier | id | Data point identifier | sales_estimate_B0CXXX1234_20260301 |
| Resource type | type | Fixed value | sales_estimate_result |
| Parent ASIN | parentAsin | Parent ASIN (variant scenario) | B0CXXX0000 |
| Is parent | isParent | Whether it is a parent product | true / false |
| Is variant | isVariant | Whether it is a variant product | true / false |
| Is standalone | isStandalone | Whether it is a standalone product (not a variant) | true / false |
| Variant list | variants | Array of variant ASINs under this parent | ["B0CX1", "B0CX2"] |
| Daily estimates | dailyEstimates | Daily data array | See below |
| Tokens consumed | costToken | Number of tokens consumed by this call | 1 |
Each object in the dailyEstimates array
| Field | API Name | Description | Example |
|---|---|---|---|
| Date | date | Data date (YYYY-MM-DD) | 2026-03-15 |
| Estimated daily sales | estimatedUnitsSold | Estimated units sold on that day | 42 |
| Latest known price | lastKnownPrice | Latest known price (USD) | 29.99 |
Supported Marketplaces
10 Amazon marketplaces:us(United States),uk(United Kingdom),de(Germany),in(India),ca(Canada),fr(France),it(Italy),es(Spain),mx(Mexico),jp(Japan). The default marketplace is us. When the user does not specify a marketplace, use us.
How to call
- API endpoint：
POST /tool-jungle-scout/sales-estimates/query(for full parameters/responses/error codes, seereferences/api.md） - Python script：
python scripts/junglescout_sales_estimates.py '<JSON 参数>' [--inline] - Cost constraints: This tool consumes compute credits; by default, the same parameter combination in the same session is called only once, and the script has a 24h local cache. On failure or empty results, do not automatically switch keywords, turn pages, or change the ZIP code to probe continuously; if you need to continue searching, first explain to the user that additional consumption will be incurred.
Output strategy (default script behavior)：
- Alwayswrite the full response to
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-junglescout-sales-estimates-<timestamp>.json（<cwd>is the working directory when the script runs, which in Claude Code is the current project directory;<session>is taken from the environment variableSESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, and if the current directory is not writable, report an error) - Response body ≤ 8 KB: after writing to disk, print the full JSON to stdout
- Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, common counts such as
total/costToken, the length of the largest list field + the first 3 samples) - Add
--inlineto force full printing to stdout (also written to disk)
Data reading recommendations: first look at the summary to determine whether it is sufficient; when specific fields are needed, prefer to use jqorConvertFrom-Json to extract on demand from the saved json file, avoiding bringing the entire JSON into context.
Resolve authentication and compute credit issues
When the following abnormal situations occur, use references/onboarding.md to guide resolution of the issue:
Abnormal situations
- API Key not configured: the environment variable is not configured
LINKFOX_AGENT_API_KEY, andLINKFOXAGENT_API_KEY。 - Response 401 or 402 status code
- Response indicates insufficient compute credits or balance: the message contains "insufficient compute credits/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.
How to Build Queries
All four parameters arerequired：marketplace、asin、startDate、endDate。
Principles for Building API Calls
- Site mapping: the user says "US site" →
us, "Japan site" →jp, "Germany site" →de; if unspecified, default tous - Date format: must be
YYYY-MM-DD, e.g.2026-03-01 - endDate restriction：
endDatemust be earlier than the current date (cannot include today or future dates) - ASIN format: standard Amazon ASIN, usually starting with B0, 10 characters in total
- Common time calculations：
- "past 30 days" → endDate is yesterday, startDate is 30 days ago
- "last month" → from the 1st of last month to the last day of last month
- "Q3 vs Q4" → call twice, querying July-September and October-December respectively
Common Query Scenarios
1. Check competitors' sales over the past 30 days
{
"marketplace": "us",
"asin": "B0CXXX1234",
"startDate": "2026-03-18",
"endDate": "2026-04-16"
}
2. Compare Q3 and Q4 sales performance
Call twice:
- Q3：
startDate=2025-07-01,endDate=2025-09-30 - Q4：
startDate=2025-10-01,endDate=2025-12-31
3. Validate product selection opportunities—check a product's full-year sales
{
"marketplace": "us",
"asin": "B0CXXX5678",
"startDate": "2025-04-01",
"endDate": "2026-03-31"
}
4. Track new product launch performance
{
"marketplace": "de",
"asin": "B0DYYY9999",
"startDate": "2026-01-15",
"endDate": "2026-04-15"
}
5. Monitor sales changes during major promotions (such as Prime Day)
{
"marketplace": "us",
"asin": "B0CXXX1234",
"startDate": "2025-07-01",
"endDate": "2025-07-21"
}
Display Rules
- Line charts preferred: it is recommended to use a line chart to show daily sales changes, with dates on the horizontal axis and estimated daily sales on the vertical axis; if price data is available, a second Y axis can be overlaid to show price trends
- Table assistance: also provide a data table for precise reference, with columns including: date, estimated sales, most recent known price
- Summary statistics: After the data, summarize key metrics—total sales, average daily sales, estimated total revenue (total sales × average price)
- Trend Summary: Briefly summarize the trend direction (rising/falling/stable/cyclical fluctuation), and note the dates of sales peaks and troughs
- Error handling: When a query fails, explain the reason based on the error response and suggest adjusting parameters (e.g., endDate cannot include today or future dates)
Important Limitations
- endDate cannot include today：
endDatemust be earlier than the current date; you cannot query sales for today or future dates - One ASIN per call: Each call can query only one ASIN; comparing multiple ASINs requires multiple calls
- All parameters are required：
marketplace、asin、startDate、endDatenone can be omitted - Prices are in USD：
lastKnownPricethe unit is USD, not local currency
User Expression & Scenario Quick Reference
Applicable - ASIN sales estimation and sales trend analysis:
| User Says | Scenario |
|---|---|
| "How many units can this ASIN sell per day" | Query recent daily sales estimates |
| "How have competitors been selling recently" | Monitor a competitor's sales over the past 30 days |
| "Is this product seasonal" | Use full-year sales data to determine seasonal patterns |
| "Help me look at this product's sales trend" | Sales trend for a specified time period |
| "How are Q4 peak season sales" | Sales query for a specific quarter |
| "Is this product worth doing" | Validate product selection opportunities through historical sales |
| "How much was sold during the big promotion" | Sales monitoring during an event |
Not applicable - Beyond the scope of ASIN sales estimation:
- Keyword search volume (requires a keyword historical search volume tool)
- BSR ranking history (requires a BSR tracking tool)
- Overall category sales/market size
- Sales data from non-Amazon platforms
- Real-time/current sales (data is delayed and does not include today)
Boundary judgment: When users say "sales", "daily sales", or "how much was sold", if they want to see a specific ASIN's daily estimated sales over a time range, this skill applies. If they want keyword search volume, category rankings, or real-time live sales, it does not apply.
Compute Power Consumption Rules
Consumes 64 compute power.
Users pay for compute power consumption. Please fully assess: when this skill needs to be called frequently, or the user has insufficient expectations for compute power consumption, be sure to remind the user and let the user decide whether to continue.
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
- The functionality or purpose described in this skill does not match actual behavior
- The skill's results do not match the user's intent
- The user expresses dissatisfaction or praise about this skill
- 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, visit LinkFox Skills.