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). 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

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.4/5.0
Behavior5/5

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

Annotations already mark the tool read-only, and the description adds substantial behavior beyond that: row fields, ASIN-scope placement data, the 'not ranking' marker, the no-marketplace 'MARKETPLACE NEEDED' failure mode, and the ask-once/reuse marketplace rule. This is exactly the kind of behavioral context an agent needs.

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 description is longer than average but every section earns its place: scope definition, row contents, usage guidance, and marketplace behavior. It is front-loaded with the core purpose. Some redundancy with the input schema, such as the 'MARKETPLACE NEEDED' and currency notes, prevents a perfect score.

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 properly explains what returned rows contain, including ASIN-specific fields and the 'not ranking' marker. It also covers the required marketplace handling and the failure mode when marketplace is omitted. This is complete enough for an agent to invoke the tool correctly.

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

Parameters3/5

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

Schema coverage is 100%, and the schema already documents asin, keyword, and marketplace in detail, including the ask-once/reuse behavior and local-currency note. The description reinforces the two-scope model but adds little parameter meaning beyond what the schema already provides, so the baseline of 3 applies.

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 names the exact data type ('keyword / SEO / PPC data') and the two distinct scopes: ASIN-scope and keyword-scope. It also distinguishes the tool from analysis-oriented siblings by explicitly stating 'Pure data fetch (no AI analysis)', so an agent can tell it apart without opening other tool schemas.

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?

It gives a concrete 'How to use' section covering SEO/PPC targeting, CPC interpretation, niche-demand summation, and organic-vs-sponsored rank checks. It also provides a clear marketplace prerequisite workflow. It stops short of explicitly naming sibling alternatives or saying when not to use this tool, but the context is otherwise clear.

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