Google AI Search
This skill calls Google Search in AI Mode to get the AI Overview answer for a single keyword. Only one question per call is supported — there is no multi-turn follow-up within a single request. The response is unstructured Markdown — summarize it directly, do not route it to a data-analysis sandbox.
Core Concepts
The tool drives Google's AI Mode (the panel that appears at the top of Google search results and synthesizes an answer with citations):
- The required
keywordis sent to Google as the query and the AI Overview for it is captured. - Single-round only: each call handles exactly one question. There is no
promptsparameter for follow-ups. - For follow-up questions: the agent must summarize the previous AI Overview answer (key points, citations, relevant context) and concatenate it with the new question into a new
keyword, then make a fresh API call. - All answers are returned as a single Markdown document under
stdout, with citations linked to the source pages.
resultsNum reports how many AI Overview blocks were rendered; 0 means the keyword did not trigger an AI Overview on Google for the requested locale.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| keyword | string | Yes | Google search keyword. Sent as the q= parameter to Google AI Mode. For follow-up questions, the agent should summarize the previous answer and concatenate with the new question into this field. |
Response Fields
| Field | Type | Description |
|---|---|---|
| stdout | string | Markdown document with the AI Overview for the keyword, plus inline citation links |
| sourceUrl | string | The Google AI Mode search URL that was actually requested |
| resultsNum | integer | Number of AI Overview blocks rendered (0 = keyword did not trigger AI Overview) |
| code / errcode | string / integer | 200 on success; non-200 indicates a business error |
| msg / errmsg | string | ok on success; otherwise an error description |
| costTime | integer | API latency in milliseconds |
| costToken | integer | Tokens consumed (only billed on success) |
| taskId | string | Upstream task identifier for tracing |
| type | string | Render hint, fixed value stdoutWorkbenches |
API Usage
This tool is exposed via the LinkFox tool gateway. See references/api.md for the calling convention, request/response shape, error codes, and a curl example. You can also run scripts/google_ai_search.py directly to test it from the command line.
How to Build Queries
Each call takes a single keyword. For follow-up questions, the agent must summarize the previous result and build a new query.
Tips
- Front-load context in
keyword: include market/region cues when relevant ("open-ear bone-conduction headphones US 2026") — the AI Overview is sensitive to phrasing. - Match the language to the target market: ask in English for US/UK/AU markets, Japanese for JP, German for DE, etc. — the AI Overview is biased toward the locale's language.
- Use natural-language questions: phrasing like "compare against" / "what are the unsolved pain points" elicits richer AI Overview output than single keywords.
- For follow-ups, summarize and re-ask: when the user wants to dig deeper, the agent should summarize key points from the previous AI Overview response and concatenate with the new question into a new
keywordfor a fresh call. Example:"Based on the AI overview that top bone-conduction headphones are Shokz OpenRun Pro and AfterShokz Aeropex, what are the unsolved technical pain points compared to in-ear earbuds?"
Usage Examples
1. Single-shot AI Overview
{
"keyword": "GaN charger vs traditional charger comparison"
}
2. Cross-border product research
{
"keyword": "best open-ear bone conduction headphones 2026 US"
}
3. Follow-up question (agent summarizes prior result and re-asks in a new call)
First call:
{
"keyword": "best open-ear bone conduction headphones 2026 US"
}
Second call (agent builds context summary + new question):
{
"keyword": "The AI overview mentioned OpenRun Pro and AfterShokz Aeropex as top picks for bone conduction headphones. What unsolved technical pain points still exist compared to in-ear earbuds?"
}
4. Consumer preference snapshot
{
"keyword": "robot vacuum buying preferences 2026 reddit"
}
5. Long-tail keyword exploration for selection
{
"keyword": "smart pet feeder for cats with camera"
}
Display Rules
- Render the Markdown directly:
stdoutis already structured Markdown with headings, bullets, and citation links — preserve that structure when answering the user. - Cite sources: keep the inline reference links from
stdoutso the user can verify each claim. - Flag empty AI Overview: if
resultsNumis0, tell the user Google AI Overview did not trigger for that keyword and suggest rephrasing or trying a different region. - Don't reroute to a data-analysis sandbox: the output is unstructured text and not suitable for SQL-like processing.
- Indicate freshness: results reflect Google AI Mode at call time; mention this when the user asks about recency.
- Handle business errors: if
code/errcodeis not200, surface themsg/errmsgto the user and suggest retrying or refining the input.
Important Limitations
- Unstructured output: Markdown text only — no structured tables, no second-pass data query.
- AI Overview not guaranteed: some keywords (especially niche, ambiguous, or sensitive ones) do not trigger AI Overview at all (
resultsNum = 0). - Single-round only: no multi-turn follow-up within one call. For follow-ups, the agent must summarize previous context and make a new call.
- Locale follows Google's defaults: the tool uses Google's standard AI Mode endpoint without an explicit region switch; bias the language and wording of
keywordto match the market you care about. - Real-time fetch: results are pulled live, so output for the same keyword can vary across calls.
User Expression & Scenario Quick Reference
Applicable — when the user wants AI-summarized live web information:
| User Says | Scenario |
|---|---|
| "用 Google AI 帮我搜...", "Google AI Overview 看下..." | Direct AI Overview lookup |
| "海外消费者对 XX 怎么看", "美国市场对 XX 的偏好" | Cross-border consumer preference |
| "XX 的最新趋势 / 痛点 / 使用场景" | Deep research |
| "顺便问一下 / 然后再追问 ..." | Follow-up needed (agent summarizes prior result and re-asks in new call) |
| "网页上对 XX 的总结", "搜索引擎里大家怎么说 XX" | Web-wide summarization |
| "长尾选品调研 / 蓝海选品方向" | Long-tail product exploration |
Not applicable — better routed elsewhere:
- Querying internal structured datasets (use the appropriate data query tool).
- Amazon ABA search-term analytics (use the ABA data explorer).
- Pulling structured product listings, prices, reviews from a specific platform (use the matching platform skill).
- Plain web search where the user only needs raw page content with no AI synthesis (use the standard web search skill).
- Image generation, image recognition, or file analysis.
Boundary judgment: when the user wants "AI 帮我汇总网上的说法" or "用谷歌搜一下", this skill applies. If the user wants to ask follow-up questions, the agent should summarize the previous answer and make a new call. If they explicitly want raw search results, structured data, or already have a specialized data source, do not use this skill.
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.
