Skip to main content
Glama

AMZScout Skill + MCP

by net.amzscout.chatbot
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). 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

TableJSON Schema
NameRequiredDescriptionDefault
asinNoASIN-scope: keywords this product ranks for.
keywordNoKeyword-scope: search data around this niche term.
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. 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."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial behavioral context beyond that: the tool fetches nothing without a marketplace and replies 'MARKETPLACE NEEDED', money is in local currency, and the mandatory output contract for the 'Account notice' paragraph. This fully informs the agent of expected side effects and response formatting.

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

Conciseness5/5

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

The description is long but every section earns its place: purpose, row contents, usage guidance, marketplace rule, and mandatory output contract. It is front-loaded with the core purpose and uses structured, scannable sentences without redundancy.

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 fully explains the shape of returned data (search volume, average sales, CPC, trend, placement fields) and the special account-notice response. It also covers the marketplace prerequisite and the 'MARKETPLACE NEEDED' failure mode, leaving no critical gap for correct invocation and interpretation.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds crucial semantics: ASIN and keyword are mutually exclusive scopes, ASIN-scope enriches rows with placement data, marketplace is practically required despite being marked optional, and currency is marketplace-dependent. These meanings are not inferable from the schema alone.

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?

The description opens with a specific verb and resource: fetches Amazon keyword/SEO/PPC data for either an ASIN-scope or keyword-scope. It clearly distinguishes the two operation modes and states that it is a pure data fetch with no AI analysis, which separates it from the analyze_* siblings.

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

Usage Guidelines4/5

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

Provides concrete 'How to use' guidance: picking high-volume/low-competition terms, using CPC as ad-cost pressure, summing search volumes for niche demand, and checking organic vs sponsored ranks. It also gives explicit marketplace-handling instructions. It does not name specific sibling tools, but the 'no AI analysis' note implicitly routes analysis use cases elsewhere.

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