Ecommerce Amazon Keyword Overview Skill for Claude

Nexscope Keyword Overview

This skill guides you on how to query and analyze keyword-level competition data on Amazon, helping sellers assess market competitiveness and supply-demand dynamics for specific keywords.

Core Concepts

The Nexscope Keyword Overview tool provides a comprehensive snapshot of competition metrics for a given keyword on Amazon. It returns the number of competing products across different placement types (organic, sponsored, video ads, brand ads, etc.), estimated weekly search volume, keyword popularity ranking, and the supply-demand ratio.

Supply-demand ratio: Calculated as total search result product count / monthly search volume. A lower ratio indicates less competition and greater opportunity. This is a key metric for identifying blue-ocean keywords.

Keyword popularity ranking: Represents where this keyword ranks among all keywords on the marketplace by monthly search volume. A smaller number means higher search popularity (rank 1 is the most popular). When a user says "ranking improved," it means the numeric value decreased; "ranking dropped" means the value increased.

Data Fields

| Field | API Name | Description |

|-------|----------|-------------|

| Keyword | keyword | The queried keyword text |

| Keyword Popularity Rank | keywordPopularityRank | Monthly search volume rank among all keywords (lower = more popular) |

| Estimated Weekly Search Volume | estimatedWeeklySearchVolume | Estimated weekly search count on Amazon |

| Supply-Demand Ratio | supplyDemandRatio | Product count / monthly search volume (lower = less competition) |

| Total Search Result Products | totalSearchResultProductCount | Total products shown under this keyword (organic + ads + recommendations) |

| Natural Search Products | naturalSearchProductCount | Products in organic search results (excluding ads) |

| Sponsored Products (SP) Count | sponsoredProductsCount | Products running Sponsored Products ads |

| Brand Ad Products | brandAdProductCount | Products running Brand Ads |

| Video Ad Products | videoAdProductCount | Products running Video Ads |

| Total Paid Advertising Products | paidAdvertisingProductCount | All PPC ad products combined (SP + Brand + Video, etc.) |

| Amazon's Choice Products | amazonChoiceProductCount | Products with the Amazon's Choice badge |

| Top Rated Products | topRatedProductCount | Products in the Top Rated recommendation section |

| Search Recommendation Products | searchRecommendationProductCount | Products recommended by Amazon during search |

| Editorial Recommendations Products | editorialRecommendationsProductCount | Products in Editorial Recommendations section |

| Recommendation Non-ad Products | recNonadProductCount | Products in recommendation slots classified as non-ad (organic recommendations) |

| Recommendation Ad Products | recAdProductCount | Products in recommendation slots classified as ads |

| Nexscope-Tracked Exposed ASINs | trackedAsinTotalCount | Deduplicated count of ASINs that Nexscope tracked with any exposure score (natural/ad/recommendation) -- upstream field totalAsinNum |

| Total Marketplace Keywords | totalMarketplaceKeywordCount | Total number of keywords in the marketplace |

| Data Period Start Date | dataPeriodStartDate | ABA week start date for the returned data (yyyy-MM-dd) |

| Data Period End Date | dataPeriodEndDate | ABA week end date for the returned data (yyyy-MM-dd) |

| Data Update Time | keywordDataUpdateTime | Last update timestamp for this keyword's data |

Supported Marketplaces

13 marketplaces: US (United States), UK (United Kingdom), DE (Germany), CA (Canada), JP (Japan), FR (France), ES (Spain), IT (Italy), MX (Mexico), AU (Australia), AE (United Arab Emirates), BR (Brazil), SA (Saudi Arabia).

Default marketplace is US. Use US when the user does not specify a marketplace. Codes outside this list will be rejected by the API pattern.

Important: The keyword parameter should ideally be in the language of the target marketplace. For example, use German keywords for DE, Japanese for JP, etc. If the user provides keywords in a different language, translate them to the marketplace's local language before querying.

How to Invoke

• API Endpoint: POST /sif/keywordOverview (complete params/response/error codes in references/api.md)
• Python Script: python scripts/amazon_keyword_overview.py '<JSON params>' [--inline]
• Cost constraint: This tool consumes credits; the same session and parameter combination is called only once by default, with a 24h local cache in the script. On failure or empty results, do not automatically retry with different keywords, pagination, or postal codes; inform the user about additional consumption before continuing to search.

Output strategy (script default behavior):

• Always write the full response to <cwd>/nexscope/<YYYY-MM-DD>/<session>/data/nexscope-sif-keyword-overview-<timestamp>.json (<cwd> is the working directory at script execution time, i.e. the current project directory in Claude Code; <session> is taken from the SESSION_ID env var, auto-grouped by user task; do not write to /tmp, error if current directory is not writable)
• Response body <= 8 KB: print full JSON to stdout after saving
• Response body > 8 KB: print only summary to stdout after saving (top-level fields, common counts like total/costToken, length of largest list field + first 3 samples)
• Add --inline to force full output to stdout (still saves to disk)

Data reading tip: Check the summary first to decide if it's enough; when specific fields are needed, prefer using jq or ConvertFrom-Json to extract from the saved json file on demand, avoiding loading the entire JSON into context.

Parameter Guide

• keyword (required): The search keyword to analyze. Should be translated to the target marketplace's language for best results. Maximum length: 1000 characters.
• country (optional): The Amazon marketplace code. Defaults to US. See Supported Marketplaces above for valid codes.
• last7d (optional, boolean, default true): Use the latest 7 days. When false, the API uses startDate/endDate.
• startDate (optional, yyyy-MM-dd): Start date for a custom window. Takes effect when last7d=false.
• endDate (optional, yyyy-MM-dd): End date paired with startDate.

Usage Examples

1. Basic keyword competition check

Query: "How competitive is the keyword 'wireless charger' on Amazon US?"

{"keyword": "wireless charger", "country": "US"}

2. Check competition in a non-US marketplace

Query: "How many competitors are there for 'Handyhulle' on Amazon Germany?"

{"keyword": "Handyhulle", "country": "DE"}

3. Supply-demand analysis for product research

Query: "What's the supply-demand ratio for 'yoga mat' in the US?"

{"keyword": "yoga mat", "country": "US"}

4. Advertising competition assessment

Query: "How many sellers are running ads on 'dog leash' in the UK?"

{"keyword": "dog leash", "country": "UK"}

5. Multi-marketplace comparison (multiple calls)

Query: "Compare the competition for 'bluetooth speaker' across US, UK, and DE"

• Call 1: {"keyword": "bluetooth speaker", "country": "US"}
• Call 2: {"keyword": "bluetooth speaker", "country": "UK"}
• Call 3: {"keyword": "Bluetooth Lautsprecher", "country": "DE"}

6. Specific date range

Query: "Competition for 'yoga mat' between 2026-03-08 and 2026-03-14"

{"keyword": "yoga mat", "country": "US", "last7d": false, "startDate": "2026-03-08", "endDate": "2026-03-14"}

Display Rules

• Present data clearly: Show query results in a well-structured table format. Include all relevant metrics the user asked about.
• Highlight key metrics: When showing results, emphasize the supply-demand ratio, keyword popularity rank, and total product count as these are the most actionable metrics.
• Ranking clarification: When displaying keyword popularity rank, remind users that lower values mean higher search popularity.
• Supply-demand interpretation: When showing the supply-demand ratio, provide context: values below 1 suggest high demand relative to supply (opportunity); values above 5 suggest a saturated market.
• Ad competition breakdown: When users ask about advertising competition, break down the total paid advertising count into its components (SP, Brand, Video) for a more detailed view.
• Error handling: When a query fails, explain the reason based on the msg field and suggest adjusting query parameters (e.g., check keyword spelling, try a different marketplace).
• Data freshness & period: Always surface keywordDataUpdateTime (last refresh) plus dataPeriodStartDate ~ dataPeriodEndDate (the ABA week the counts describe). Do not present product counts without naming the period.
• No subjective advice: Present data objectively without making business recommendations unless specifically asked.

Important Limitations

• Single keyword per request: Each API call queries one keyword at a time. For multi-keyword comparisons, make separate calls.
• Single record response: The API typically returns one data record per keyword (total is usually 1).
• Marketplace coverage: 13 Amazon marketplaces -- IN / NL / SE / PL / TR / SG are no longer supported. Keywords not found in the queried marketplace will return empty results.
• Time window: Defaults to the latest 7 days. Pass last7d=false plus startDate/endDate for a custom ABA week range.
• Keyword language: For best accuracy, keywords should be in the local language of the target marketplace.

User Expression & Scenario Quick Reference

Applicable -- Keyword-level competition and market assessment:

| User Says | Scenario |

|-----------|----------|

| "How competitive is XX keyword" | Competition intensity check |

| "How many products are there for XX" | Search result product count |

| "What's the supply-demand ratio for XX" | Supply-demand analysis |

| "How many sellers are advertising on XX" | Ad competition assessment |

| "Is XX keyword a blue ocean" | Market opportunity evaluation |

| "Search volume for XX keyword" | Search popularity estimation |

| "How popular is XX keyword on Amazon" | Keyword popularity ranking |

| "Compare competition across marketplaces" | Multi-market competition comparison |

| "How many Nexscope-tracked ASINs are active on this keyword" | Deduplicated tracked-ASIN count (trackedAsinTotalCount) |

| "Competition for this keyword in a specific week" | Custom date range via startDate/endDate |

Not applicable -- Needs beyond keyword competition overview:

• Historical keyword ranking trends over time (use ABA Data Explorer instead)
• Click share and conversion share by ASIN (use ABA Data Explorer instead)
• Advertising bid strategy and PPC optimization
• Product reviews, listing optimization
• ASIN-level sales estimation
• Detailed keyword search trend analysis over weeks/months

Authentication

Set the NEXSCOPE_API_KEY environment variable. If credentials are missing or expire, visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to top up credits.