Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
linkfox-ai avatar

Linkfox Junglescout Keyword History

  • 234 installs
  • 64 repo stars
  • Updated August 3, 2026
  • linkfox-ai/linkfox-skills

Helps with ai & agent building tasks.

About

linkfox-junglescout-keyword-history is a Claude Code skill in the AI & Agent Building category.

  • linkfox-junglescout-keyword-history
  • AI & Agent Building
  • AI-coding skill

Linkfox Junglescout Keyword History by the numbers

  • 234 all-time installs (skills.sh)
  • +36 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #2,652 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/linkfox-ai/linkfox-skills --skill linkfox-junglescout-keyword-history

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs234
repo stars64
Last updatedAugust 3, 2026
Repositorylinkfox-ai/linkfox-skills

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Jungle Scout — 关键词历史搜索量

This skill queries the historical exact search volume for Amazon keywords via the Jungle Scout data source, returning weekly search volume data points over a specified date range across 10 Amazon marketplaces.

Core Concepts

Jungle Scout 关键词历史搜索量工具提供亚马逊各站点关键词的周维度精确匹配搜索量历史数据。卖家可以通过查询指定时间范围内的搜索量变化来判断:

  • 季节性规律:关键词在哪些月份是旺季/淡季
  • 趋势方向:搜索量是持续上升、下降还是平稳
  • 波动幅度:判断市场需求的稳定性
  • 节假日效应:大促、节日前后的搜索量飙升

数据粒度:每条记录代表一个 7 天周期,包含该周内的精确匹配搜索量估算值。

Data Fields

Output Fields

FieldAPI NameDescriptionExample
周期标识id数据周期标识(市场/关键词/日期范围)us_sushi_20250105_20250111
周期开始日期estimateStartDate7天统计周期的起点2025-01-05
周期结束日期estimateEndDate7天统计周期的终点2025-01-11
精确搜索量estimatedExactSearchVolume该周期内精确匹配搜索量(次/周)12500
资源类型type固定值historical_keyword_search_volume
消耗TokencostToken本次调用消耗的 token 数1

Supported Marketplaces

站点marketplace 值说明
美国usAmazon.com
英国ukAmazon.co.uk
德国deAmazon.de
印度inAmazon.in
加拿大caAmazon.ca
法国frAmazon.fr
意大利itAmazon.it
西班牙esAmazon.es
墨西哥mxAmazon.com.mx
日本jpAmazon.co.jp

默认站点为 us。当用户未指定站点时,使用 us。

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/junglescout_keyword_history.py directly to run queries.

How to Build Queries

所有四个参数均为必填marketplacekeywordstartDateendDate

Principles for Building API Calls

1. 站点映射:用户说"美国站"→ us,"日本站"→ jp,"德国站"→ de;未指定时默认 us 2. 日期格式:必须为 YYYY-MM-DD,如 2025-01-05 3. 时间跨度startDateendDate 最长 366 天;超过时需拆分为多次请求 4. 关键词:原样传入用户提供的关键词(英文小写为佳) 5. 常用时间推算

  • "过去3个月" → endDate 取今天,startDate 取约90天前
  • "去年全年" → 2025-01-012025-12-31
  • "旺季" → 根据品类判断,如 Q4 为 10-0112-31

Common Query Scenarios

1. 查看关键词近半年搜索趋势

{
  "marketplace": "us",
  "keyword": "yoga mat",
  "startDate": "2025-10-01",
  "endDate": "2026-03-31"
}

2. 判断关键词季节性(查全年数据)

{
  "marketplace": "us",
  "keyword": "christmas decorations",
  "startDate": "2025-01-01",
  "endDate": "2025-12-31"
}

3. 对比旺季与淡季搜索量

分两次调用:

  • 淡季:startDate=2025-02-01, endDate=2025-04-30
  • 旺季:startDate=2025-10-01, endDate=2025-12-31

4. 多站点对比

对同一关键词分别查询不同 marketplace(如 usdejp),比较各站搜索量规模。

5. 验证市场需求是否增长

{
  "marketplace": "de",
  "keyword": "luftreiniger",
  "startDate": "2025-04-01",
  "endDate": "2026-03-31"
}

Display Rules

1. 趋势可视化优先:建议以时间线/折线图方式展示搜索量变化,横轴为日期周期,纵轴为搜索量 2. 表格辅助:同时提供数据表格供精确查阅,列包括:周期开始日期、周期结束日期、搜索量 3. 趋势总结:在数据之后简要总结趋势方向(上升/下降/平稳/周期性波动),标注峰值和谷值周期 4. 峰值标注:高亮搜索量最高和最低的周期,便于用户快速判断旺淡季 5. Error handling: When a query fails, explain the reason based on the error response and suggest adjusting parameters(如日期范围超 366 天)

Important Limitations

  • 时间跨度上限:单次查询 startDateendDate 最长 366 天,超过需拆分查询
  • 数据粒度:周维度(7天一个数据点),非日维度
  • 搜索量类型:精确匹配搜索量(Exact Match),非广泛匹配
  • 所有参数必填marketplacekeywordstartDateendDate 缺一不可

User Expression & Scenario Quick Reference

Applicable - 关键词搜索量历史趋势分析:

User SaysScenario
"这个词搜索量怎么变化的"搜索量趋势查询
"这个品类有没有季节性"全年数据判断季节规律
"搜索量最近在涨还是跌"近期趋势判断
"什么时候是旺季"峰值周期识别
"去年Q4搜索量多少"指定时间段搜索量查询
"这个词在德国站热不热"非美国站搜索量查询
"对比两个时间段的搜索量"旺淡季/同比对比

Not applicable - 超出关键词历史搜索量范围:

  • 关键词建议/拓词(需要关键词挖掘工具)
  • 实时/当前搜索量排名(需要 ABA 或 SIF 工具)
  • 关键词竞争度、CPC 出价
  • 商品销量、listing 分析
  • 非亚马逊平台的搜索量

Boundary judgment: When users say "搜索量", "关键词热度", or "市场需求趋势", if they specifically want to see how a keyword's search volume changes over a period of time (historical trend), this skill applies. If they want the current ranking or a list of trending keywords, it does not apply.

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.

<!-- LF_LARGE_RESPONSE_BLOCK -->

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/junglescout_keyword_history.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. <!-- /LF_LARGE_RESPONSE_BLOCK -->

--- For more high-quality, professional cross-border e-commerce skills, visit [LinkFox Skills](https://skill.linkfox.com/).

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.