Skip to main content
Glama

AMZScout Skill + MCP

by io.github.amzscout-corp
OverviewDiscussionsAdmin

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.

Input Schema

NameRequiredDescriptionDefault
asinNoASIN-scope: keywords this product ranks for. Together with `keyword`: this product's position for exactly that keyword.
keywordNoKeyword-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).
marketplaceNoAmazon 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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)."
  2. Changed1 schema field changed
    • 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."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly), but the description adds substantial behavioral context: the exact-match row semantics, the look-alike caveat, and critically that omitting `marketplace` fetches nothing and returns 'MARKETPLACE NEEDED'. It also discloses the local-currency behavior of monetary fields.

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?

The core mode distinction is front-loaded and every sentence carries information given the tool's dual-mode complexity. It is on the long side and the marketplace requirement is restated in both description and schema, costing some tightness.

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?

With no output schema, the description carries the return-shape burden and does so: keyword rows carry search volume, average sales, CPC and trend; ASIN-scope rows add organic rank/page, sponsored page, and relevance score. Nothing an agent needs to call it correctly is missing.

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% and schema descriptions are already detailed, so the baseline is 3. The description adds genuine meaning beyond the schema by explaining the combined asin+keyword exact-match behavior and the 'never report a look-alike's rank' constraint, which the schema does not convey.

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?

States a specific verb (fetch keyword/SEO/PPC data) and resource, and crisply distinguishes its two operating modes (ASIN-scope vs keyword-scope) plus the both-params case. An agent can tell exactly what this returns versus sibling analyze_* tools.

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?

Explicit when-to-use guidance: how to select high-volume/low-competition terms, use CPC for ad-cost pressure, sum volumes for niche demand, and check organic vs sponsored ranks for ASIN-scope. It also contrasts itself as a 'pure data fetch (no AI analysis)' against analysis siblings, and gives the marketplace ask-once-then-reuse rule.

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 toolsInspect
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