SuperAPI AI Directory

linkfox-jiimore-niche-by-keyword

Data & analytics

View repository

Updated 10-16 00:00

About this skill

Jiimore Niche Info by Keyword

This skill guides you on how to query and analyze Amazon niche market data by keyword, helping Amazon sellers evaluate market segments for competitive intensity, brand maturity, pricing structure, and entry opportunity.

Core Concepts

A niche (sub-market segment) is a grouping of products that share a common keyword theme on Amazon. This tool returns rich analytical dimensions for each niche, including search volume, sales volume, click-through rates, brand count, top-brand concentration, new product launch success rates, CPC estimates, and a composite demand score. Data is available for US, JP, and DE marketplaces.

Keyword is required: Every query must include a keyword. The keyword should be provided in the language of the target marketplace (e.g., English for US, Japanese for JP, German for DE). When the user provides a keyword in a different language, translate it to the marketplace language before calling the API.

Percentage fields: Several parameters and response fields use a 0-1 decimal range representing 0%-100%. When displaying these values to users, convert them to percentages (e.g., 0.35 -> 35%).

Demand score: The demand field is a composite opportunity score assigned to each niche. A higher value indicates greater market demand potential.

Parameter Guide

Required

Parameter Type Description
keyword string Search keyword (max 1000 chars). Translate to the target marketplace language.

Marketplace & Pagination

Parameter Type Default Description
countryCode string US Country code: US, JP, DE
page integer 1 Page number (starts from 1)
pageSize integer 50 Results per page (10-100)
sortField string unitsSoldT7 Field to sort by (see Sorting Options below)
sortType string desc Sort direction: desc or asc

Filter Parameters (all optional, min/max ranges)

Product & Pricing:

Parameter Type Description
productCountMin / productCountMax integer Product count range
avgPriceMin / avgPriceMax number Average price range

Search & Sales (7-day):

Parameter Type Description
searchVolumeT7Min / searchVolumeT7Max integer Weekly search volume range
unitsSoldT7Min / unitsSoldT7Max integer Weekly units sold range
clickCountT7Min / clickCountT7Max integer Weekly click count range
clickConversionRateT7Min / clickConversionRateT7Max number Weekly click conversion rate (0-1)

Brand Metrics:

Parameter Type Description
brandCountMin / brandCountMax integer Number of brands in niche
top5BrandsClickShareMin / top5BrandsClickShareMax number Top 5 brands click share (0-1)
avgBrandAgeMin / avgBrandAgeMax number Average brand age (current)
avgBrandAgeQoqMin / avgBrandAgeQoqMax number Average brand age (90-day)
avgBrandAgeYoyMin / avgBrandAgeYoyMax number Average brand age (360-day)

Seller Metrics:

Parameter Type Description
avgSellingPartnerAgeMin / avgSellingPartnerAgeMax number Average seller age (current)
avgSellingPartnerAgeQoqMin / avgSellingPartnerAgeQoqMax number Average seller age (90-day)
avgSellingPartnerAgeYoyMin / avgSellingPartnerAgeYoyMax number Average seller age (360-day)

Competition & Advertising:

Parameter Type Description
top5ProductsClickShareMin / top5ProductsClickShareMax number Top 5 products click share (0-1)
sponsoredProductsPercentageMin / sponsoredProductsPercentageMax number SP ad percentage (0-1)
cpcMediumMin / cpcMediumMax number CPC median value range

New Product & Returns:

Parameter Type Description
launchRateT180Min / launchRateT180Max number 180-day new product success rate (0-1)
newProductRateT180 number 180-day new product ratio minimum (0-1)
returnRateT360Min / returnRateT360Max number 360-day return rate (0-1)

Sorting Options

Value Meaning
unitsSoldT7 Weekly units sold
searchVolumeT7 Weekly search volume
demand Demand score
avgPrice Average price
maximumPrice Maximum price
minimumPrice Minimum price
productCount Product count
searchConversionRateT7 Weekly search conversion rate
clickConversionRateT7 Weekly click conversion rate
searchVolumeGrowthT7 Search volume growth rate
clickCountT7 Weekly click count
clickCountT90 90-day click count
brandCount Brand count
top5BrandsClickShare Top 5 brands click share
top5ProductsClickShare Top 5 products click share
newProductsLaunchedT180 180-day new products launched
successfulLaunchesT180 180-day successful launches
launchRateT180 180-day launch success rate
returnRateT360 Annual return rate
clickConversionRateT90 90-day click conversion rate
searchConversionRateT90 90-day search conversion rate
searchVolumeT90 90-day search volume
unitsSoldT90 90-day units sold
unitsSoldGrowthT90 90-day sales growth rate
searchVolumeGrowthT90 90-day search volume growth rate
acos Advertising cost of sales
profitRate50 Profit margin at 50% organic sales

Usage Examples

1. Basic niche exploration by keyword Query niches related to "wireless earbuds" in the US market, sorted by weekly sales volume:

{
  "keyword": "wireless earbuds",
  "countryCode": "US",
  "sortField": "unitsSoldT7",
  "sortType": "desc"
}

2. Low-competition niche discovery Find niches for "yoga mat" where the top 5 brands hold less than 50% click share and brand count exceeds 20:

{
  "keyword": "yoga mat",
  "countryCode": "US",
  "top5BrandsClickShareMax": 0.5,
  "brandCountMin": 20,
  "sortField": "demand",
  "sortType": "desc"
}

3. High-demand, high-conversion niches Find niches for "phone case" with weekly search volume above 10000 and click conversion rate above 10%:

{
  "keyword": "phone case",
  "countryCode": "US",
  "searchVolumeT7Min": 10000,
  "clickConversionRateT7Min": 0.1,
  "sortField": "searchVolumeT7",
  "sortType": "desc"
}

4. New product opportunity analysis Find niches for "LED light" with high new product success rate (above 20%) and low return rate (below 5%):

{
  "keyword": "LED light",
  "countryCode": "US",
  "launchRateT180Min": 0.2,
  "returnRateT360Max": 0.05,
  "sortField": "launchRateT180",
  "sortType": "desc"
}

5. Japanese market niche research Explore niches related to headphones in Japan, sorted by demand score:

{
  "keyword": "\u30d8\u30c3\u30c9\u30db\u30f3",
  "countryCode": "JP",
  "sortField": "demand",
  "sortType": "desc"
}

6. Price-range-specific niche analysis Find niches for "backpack" with average price between $20 and $50 and low advertising saturation:

{
  "keyword": "backpack",
  "countryCode": "US",
  "avgPriceMin": 20,
  "avgPriceMax": 50,
  "sponsoredProductsPercentageMax": 0.3,
  "sortField": "unitsSoldT7",
  "sortType": "desc"
}

Display Rules

  1. Present data clearly: Show query results in well-structured tables. Convert decimal ratios to percentages for readability (e.g., 0.25 -> 25%).
  2. Highlight key metrics: Always surface the niche title, demand score, weekly search volume, weekly sales, brand count, and top 5 brands click share as primary columns.
  3. Translate niche titles: When the translationZh field is present and the user prefers Chinese, show it alongside the original nicheTitle.
  4. Pagination guidance: When total exceeds the current page size, inform the user of the total count and suggest fetching additional pages if needed.
  5. Error handling: When a query fails, explain the reason based on the response message and suggest adjusting filter criteria (e.g., broadening ranges or checking the keyword).
  6. CPC display: When CPC data is present, show all three tiers (low, medium, high) to give a complete advertising cost picture.
  7. No subjective advice: Present data objectively without adding unsolicited business recommendations. Only provide interpretation when explicitly requested by the user.

Important Limitations

  • Supported marketplaces: Only US, JP, and DE are available. Other marketplace codes will be rejected.
  • Keyword required: Every query must include a keyword. The API will not return results without one.
  • Result cap: Maximum 100 results per page.
  • Percentage values: All rate/share parameters use 0-1 range, not 0-100. Ensure correct values when constructing filters.

User Expression & Scenario Quick Reference

Applicable -- Niche-level market segment analysis by keyword:

User Says Scenario
"Is there opportunity in the XX market" Niche opportunity assessment
"How competitive is XX keyword" Monopoly / brand concentration
"Find low-competition niches for XX" Blue ocean niche discovery
"What's the new product success rate for XX" New entrant viability
"Show me niche data for XX" General niche exploration
"Which XX niches have high demand" Demand-driven niche ranking
"What's the CPC / ad cost for XX niches" Advertising cost analysis
"Find niches with high conversion for XX" Conversion-optimized segments
"Brand concentration in XX market" Brand dominance assessment

Not applicable -- Needs beyond niche-level segment data:

  • Individual ASIN performance or sales estimation
  • Search term ranking trends (use ABA data tools instead)
  • Advertising campaign management or bid optimization
  • Product review analysis or listing optimization
  • Supplier sourcing or logistics planning

Boundary judgment: When users say "market research" or "product opportunity", if their intent focuses on evaluating the competitive landscape and demand potential of keyword-level market segments, this skill applies. If they need ASIN-level data, search term ranking trends, or comprehensive business strategy, direct them to the appropriate tool.

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.

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/jiimore_get_niche_info_by_keyword.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"

Pick --out-dir outside any git working tree (e.g. /tmp/... on Unix, %TEMP%/... on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

  • High field count per record, or fields you don't need
  • Batch/paginated results (multiple items per call)
  • Long-text fields (descriptions, reviews, HTML, time series)
  • Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read.


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