Amazon Search Intelligence SF
Amazon Keyword Overview MCP
Evaluate search demand and competition for an Amazon keyword. Call the Amazon Keyword Overview API via REST or MCP with your Nexscope API key.
Amazon Keyword Overview AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Check Keyword Demand
Prompt: Show available search demand and competition for [KEYWORD] on Amazon in [MARKETPLACE].
2. Check The Latest Seven Days
Prompt: Show available search demand and competition for [KEYWORD] on Amazon in [MARKETPLACE]. Use the latest seven-day reporting window.
3. Check A Custom Reporting Period
Prompt: Show available search demand and competition for [KEYWORD] on Amazon in [MARKETPLACE]. Use the reporting period from [START_DATE] through [END_DATE] instead of the latest seven days. Keep the returned coverage and dates explicit.
What You Need to Provide
Replace the bracketed placeholders with your own research inputs. Keep source estimates, reporting periods and missing information explicit.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
nexscope_amazon_keyword_overviewhttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "amazon-keyword-overview-1",
"method": "tools/call",
"params": {
"name": "nexscope_amazon_keyword_overview",
"arguments": {
"country": "US",
"keyword": "phone case",
"last7d": true
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
keyword | string | required | Keyword, translate to the corresponding country's language whenever possible. Max length: 1000 characters Example: phone case |
country | string | optional | Country site, default US. Options (13 total): US, UK, DE, CA, JP, FR, ES, IT, MX, AU, AE, BR, SA |
last7d | boolean | optional | Whether to get last 7 days data, default true. When false, use startDate/endDate range Example: true |
startDate | string | optional | Start date yyyy-MM-dd (effective when last7d=false) Example: 2026-01-01 |
endDate | string | optional | End date yyyy-MM-dd (paired with startDate) Example: 2026-01-01 |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
msg | string | optional | news |
total | integer | optional | Total amount of data, usually 1 |
code | string | optional | sf business return code, `"1"` indicates success |
data | array | optional | keyword overview array |
costTime | integer | optional | Time consuming (ms) |
costToken | integer | optional | Consume token |
columns | array | optional | render column |
type | string | optional | rendering style |
title | string | optional | Title |
keyword | string | optional | keywords |
keywordPopularityRank | integer | optional | Keyword popularity ranking. The smaller the value, the greater the search volume. |
estimatedWeeklySearchVolume | integer | optional | Estimated search volume per week |
supplyDemandRatio | number | optional | Supply and demand ratio (number of search results products / monthly search volume), the smaller the value, the smaller the competition and the greater the opportunity. |
totalSearchResultProductCount | integer | optional | Total number of search results items |
naturalSearchProductCount | integer | optional | Number of natural search items |
sponsoredProductsCount | integer | optional | SP number of advertised items |
brandAdProductCount | integer | optional | Number of brand advertising products |
videoAdProductCount | integer | optional | Number of video advertising products |
paidAdvertisingProductCount | integer | optional | Total number of PPC paid advertising products |
amazonChoiceProductCount | integer | optional | Amazon's Choice item count |
topRatedProductCount | integer | optional | Top Rated number of items |
searchRecommendationProductCount | integer | optional | Search the number of recommended products |
editorialRecommendationsProductCount | integer | optional | Number of items recommended by editors |
recNonadProductCount | integer | optional | Number of recommended non-advertising products |
recAdProductCount | integer | optional | Number of recommended advertising products |
trackedAsinTotalCount | integer | optional | The total number of exposed ASIN deduplication tracked by sf; the upstream field is `totalAsinNum` |
totalMarketplaceKeywordCount | integer | optional | Total number of site keywords |
dataPeriodStartDate | string | optional | Data period start date |
dataPeriodEndDate | string | optional | Data period end date |
keywordDataUpdateTime | string | optional | Keyword data update time |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Summarize demand for “phone case” on Amazon US over the last seven days.
Illustrative Response Explanation
The illustrative result reports estimated weekly search volume of 2,000 and 500 search-result products. Search demand and product counts describe different measures; neither is a sales total.
About this sample: Illustrative example only. Names, identifiers and numbers are fictional; no live tool call was made. Your results depend on your account, inputs and available data.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
View the MCP Request & Response Format
Examples
Illustrative example with fictional data, not a live tool call.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
{
"jsonrpc": "2.0",
"id": "amazon-keyword-overview-example",
"method": "tools/call",
"params": {
"name": "nexscope_amazon_keyword_overview",
"arguments": {
"country": "US",
"keyword": "phone case",
"last7d": true
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "amazon-keyword-overview-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"data\":[{\"keyword\":\"phone case\",\"estimatedWeeklySearchVolume\":2000,\"totalSearchResultProductCount\":500}],\"total\":1}}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"data": [
{
"keyword": "phone case",
"estimatedWeeklySearchVolume": 2000,
"totalSearchResultProductCount": 500
}
],
"total": 1
}
},
"isError": false
}
}