AMZScout Skill + MCP

amzscout_get_keywords

Read-only

Amazon keyword / SEO / PPC data for either a single product (ASIN-scope — terms the product ranks for) or a niche/category (keyword-scope — search data around the term). Pass BOTH asin and keyword to get the product's position for exactly that keyword (e.g. "organic rank of B0... for standing lamp") — the reply gives the exact-match row as the answer and lists look-alike keywords with extra symbols separately; never report a look-alike's rank for the requested keyword. Every keyword row carries search volume, average sales, CPC and trend; ASIN-scope rows ALSO carry this product's own placement for that term — organic rank + page, sponsored page, and relevance score (rows the product does not rank for are marked "not ranking"). Pure data fetch (no AI analysis). How to use: pick high-volume / low-competition terms for SEO and PPC targeting, use CPC as ad-cost pressure, sum search volumes to gauge niche demand, and for ASIN-scope check organic vs sponsored ranks to spot listing-optimization gaps. Marketplace: if the user has not named a country / Amazon domain in this conversation, ask them once which marketplace they work on and reuse that code for every later call in the chat; do not assume the US. Called without marketplace, this tool fetches nothing and answers "MARKETPLACE NEEDED". Money is in that marketplace's local currency. OUTPUT CONTRACT (mandatory): if the result begins with an "Account notice:" paragraph, your reply MUST begin with that exact paragraph copied verbatim — including the View Plans markdown link — before any analysis. If the result is ONLY that paragraph, it is your entire reply. Never omit, shorten, or paraphrase it.

Input Schema

Name	Required	Description
`asin`	No	ASIN-scope: keywords this product ranks for. Together with `keyword`: this product's position for exactly that keyword.
`count`	No	How many keywords to return (1–200). Default: 200 for keyword-scope, 100 for ASIN-scope (ASIN-scope returns at most 100). Billed per keyword returned — ask only for what you need. Ignored for the ASIN+keyword position lookup.
`keyword`	No	Keyword-scope: search data around this niche term. Together with `asin`: the exact keyword to look up for the product (pass it exactly as the user wrote it — no added symbols or words).
`marketplace`	No	Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools fetch nothing and answer "MARKETPLACE NEEDED". Money in results is in this marketplace's currency.
`includeHistory`	No	Include per-keyword monthly *History series (search volume, sales, rank). Default true. Billed +300 per keyword that carries history where the series are delivered; pass false when current values are enough.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / properties / count

Added value: +{
+  "description": "How many keywords to return (1–200). Default: 200 for keyword-scope, 100 for ASIN-scope (ASIN-scope returns at most 100). Billed per keyword returned — ask only for what you need. Ignored for the ASIN+keyword position lookup.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / includeHistory

Added value: +{
+  "description": "Include per-keyword monthly *History series (search volume, sales, rank). Default true. Billed +300 per keyword that carries history where the series are delivered; pass false when current values are enough.",
+  "type": "boolean"
+}

Changed2 schema fields changedOct 5, 2026

changedInput schema / properties / asin / description

Previous value: -"ASIN-scope: keywords this product ranks for."New value: +"ASIN-scope: keywords this product ranks for. Together with `keyword`: this product's position for exactly that keyword."

changedInput schema / properties / keyword / description

Previous value: -"Keyword-scope: search data around this niche term."New value: +"Keyword-scope: search data around this niche term. Together with `asin`: the exact keyword to look up for the product (pass it exactly as the user wrote it — no added symbols or words)."

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / marketplace / description

Previous value: -"Amazon marketplace code. Default COM (United States)."New value: +"Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools fetch nothing and answer \"MARKETPLACE NEEDED\". Money in results is in this marketplace's currency."

First observedAug 3, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the readOnly/openWorld annotations: discloses billing behavior (per-keyword charges, +300 for history), the currency of monetary values, the failure mode when marketplace is missing, and a mandatory output contract for 'Account notice:' text. Minor deduction because the exact response shape (row fields layout) is only sketched, not fully enumerated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: purpose and mode split come first, then usage, then marketplace rule, then output contract. Some redundancy (marketplace/currency repeated from the schema description; 'MARKETPLACE NEEDED' stated twice) costs a point, but no sentence is truly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description covers what rows contain (search volume, average sales, CPC, trend, plus organic rank/page, sponsored page, relevance score for ASIN-scope), including the 'not ranking' marker and the look-alike separation rule. Combined with the marketplace prerequisite and output contract, an agent has everything needed to call and interpret it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description nevertheless adds value by explaining how asin and keyword interact and warning not to add symbols/words to the keyword and never to report a look-alike's rank for the requested term. Repetition of marketing-style usage notes rather than parameter edge cases keeps it at 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Amazon keyword / SEO / PPC data') and immediately splits the two operating modes (ASIN-scope = terms the product ranks for; keyword-scope = search data around the term), including the combined ASIN+keyword exact-position mode. This distinguishes it clearly from siblings like amzscout_analyze_niche and amzscout_analyze_product.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit mode selection (pass both params for position lookup) and interpretive guidance (pick high-volume/low-competition terms, use CPC as ad-cost pressure, sum volumes for niche demand, compare organic vs sponsored ranks). Also states the prerequisite that a marketplace must be named or asked for, and that omitting it yields 'MARKETPLACE NEEDED'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AMZScout Skill + MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?