linkfox-google-trend-get-trend-by-time

Google Trends Time-Range Analysis

This skill guides you on how to query and analyze Google Trends data for trending topics within a configurable time window, helping users discover real-time popular searches and emerging trends across 18 supported regions.

Core Concepts

Google Trends reflects real user search interest on Google. This tool retrieves trending topics (recently popular queries) for a chosen country/region over a specified number of recent days. It is ideal for spotting what is currently gaining traction in a market.

Key data points per trending query:

• query -- the trending search term
• searchVolume -- relative search volume value
• increasePercentage -- percentage change in search interest (-100 to 100, unit: %)
• startTime / endTime -- timestamps bounding the trend observation window

A positive increasePercentage means rising interest; a negative value means declining interest. A value near 100 signals an explosive spike.

Parameter Guide

Supported Regions

US (United States), GB (United Kingdom), JP (Japan), CA (Canada), MX (Mexico), DE (Germany), FR (France), IT (Italy), ES (Spain), NL (Netherlands), AU (Australia), SG (Singapore), AE (United Arab Emirates), BR (Brazil), IN (India), TR (Turkey), PL (Poland), SE (Sweden)

Default region is US. Use US when the user does not specify a region.

调用方式

• API 端点：POST /googleTrend/getTrendByTime（完整参数/响应/错误码见 references/api.md）
• Python 脚本：python scripts/google_trends_rising.py '<JSON 参数>' [--inline]
• 成本约束：本工具会消耗算力；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。

输出策略（脚本默认行为）：

• 始终将完整响应写入 <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-google-trend-get-trend-by-time-<timestamp>.json（<cwd> 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；<session> 取自环境变量 SESSION_ID，按用户任务自动聚合；禁止写入 /tmp，当前目录不可写则报错）
• 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout
• 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 total/costToken、最大列表字段的长度 + 前 3 条样本）
• 加 --inline 强制全量打印到 stdout（同样落盘）

读数据建议：先看摘要判断是否足够；需要具体字段时优先用 jq或ConvertFrom-Json 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。

解决认证和算力问题

发生以下异常情况时，采用 references/onboarding.md 引导解决问题：

异常情况

• 未配置API Key：环境变量未配置 LINKFOX_AGENT_API_KEY，也未配置 LINKFOXAGENT_API_KEY。
• 响应401或402状态码
• 响应提示算力或余额不足：消息含"算力余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值"，或类似含义的内容。

Usage Examples

1. What's trending in the US over the past week?

{"days": 7, "region": "US"}

2. Hot topics in Japan in the last 24 hours

{"days": 1, "region": "JP"}

3. Trending searches in Germany over the past 2 days

{"days": 2, "region": "DE"}

4. Recent buzz in Brazil this week

{"days": 7, "region": "BR"}

5. What's gaining popularity in the UK right now?

{"days": 1, "region": "GB"}

Display Rules

1. Present data clearly: Show trending queries in a well-formatted table with columns for query, search volume, and increase percentage. Sort by search volume or increase percentage as appropriate.
2. Highlight spikes: When increasePercentage is notably high (e.g., above 50%), call attention to these breakout topics.
3. Time context: Always state the time range and region in your summary so the user knows exactly what window the data covers.
4. Chart data: If the response includes chartOption, describe the chart structure (title, axes, data points) so the user understands the visual trend.
5. Error handling: When a query fails, explain the reason based on the error response and suggest adjusting parameters (e.g., try a different region code or time range).

Important Limitations

• Data analysis: The response is JSON. Read chartOption.data from the saved response to filter or sort the returned rows. _dataQuery_executeDynamicQuery queries Linkfox session data stored in SLS; it is not a general JSON-file reader, so do not pass this response to it without a supported stored-data mapping.
• Relative volumes: Search volume values are relative, not absolute counts.
• Short time windows: The days parameter controls recency; this tool is designed for recent/real-time trends, not long historical analysis.
• Region coverage: Only the 18 listed regions are supported. Unsupported region codes will produce errors.

User Expression & Scenario Quick Reference

Applicable -- Queries about trending/popular topics on Google:

Not applicable -- Needs beyond trending topic discovery:

• Historical keyword search volume over months/years (use a dedicated Google Trends historical tool)
• Amazon-specific keyword or ASIN analysis (use ABA tools)
• Advertising / PPC campaign management
• Social media trend analysis (Twitter/X, TikTok, etc.)
• SEO ranking or backlink analysis
• Competitor website traffic estimation

Boundary judgment: When users say "market trends" or "what's popular", if it boils down to discovering what people are currently searching for on Google in a specific region, this skill applies. If they are asking about stock market trends, social media virality, or long-term historical search patterns, it does not apply.

算力消耗规则

消耗 6 算力。

用户会因算力消耗而支付费用。请充分评估：当需要高频调用本技能，或用户对算力消耗量预期不足时，务必提醒用户，由用户决定是否继续。

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](https://skill.linkfox.com/).