Nexscope

Amazon Research JS

Amazon Keyword Search History MCP

Track exact Amazon keyword search volume in seven-day periods across 10 marketplaces. Call via REST API or MCP with your Nexscope API key.

CostRecent Avg. 133 · Range 67–133 credits / callOnline Test

Amazon Keyword Search History 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 Historical Search Volume

Prompt: Show the recorded search volume for [KEYWORD] on Amazon in [MARKETPLACE] from [START_DATE] to [END_DATE], using a range of at most 366 days. Keep the source’s seven-day reporting periods.

2. Check Gaps In The Reporting Calendar

Prompt: Show the recorded search volume for [KEYWORD] on Amazon in [MARKETPLACE] from [START_DATE] to [END_DATE], using a range of at most 366 days. Keep the source’s seven-day reporting periods. List the returned seven-day start and end dates and identify gaps or overlapping periods inside my requested range. Do not fill absent periods with zero or invent a numerical volume field.

3. Review Changes In Weekly Search Estimates

Prompt: Show Amazon keyword [keyword] in [supported marketplace] from [start date] to [end date], spanning at most 366 days. If the weekly exact-search estimates shown in the published example are returned, plot them against their seven-day windows and flag the largest observed increases. Compute differences only between consecutive complete windows; leave missing estimates blank and label the values as estimates.

What You Need to Provide

Replace the bracketed placeholders with your own research inputs. Keep source estimates, reporting periods and missing information explicit.

The published example includes weekly exact-search estimates, but the response-field list omits that metric. Trend analysis is conditional on it being returned; no value is guaranteed for every week.