Skip to main content
Glama

AMZScout Skill + MCP

by net.amzscout.chatbot
OverviewDiscussionsAdmin

amzscout_analyze_product

Read-only

Full raw data for a single Amazon product by ASIN — price, estimated sales/revenue, reviews, rating, listing quality, sellers, plus sales/price/revenue history when available. Pure data fetch (no AI analysis) — reason over the returned data yourself. How to use: audit the product like a sourcing analyst — demand trend & seasonality from sales history, pricing direction & margin risk from price history and FBA fees, competition from sellers/reviews, listing quality from LQS, then conclude whether a new seller should enter (GO / NO-GO and what it would take). 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
asinYesAmazon Standard Identification Number
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.6/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 meaningful behavior beyond that: no AI analysis, no fetch without marketplace with the exact 'MARKETPLACE NEEDED' response, local-currency handling, reuse of the chosen marketplace, and the mandatory Account notice output contract. No contradiction with annotations.

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 is organized into logical sections: overview, how to use, marketplace, and output contract. It front-loads the core purpose and only repeats the local-currency point once more than necessary.

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 burden of explaining what the tool returns, listing price, sales/revenue, reviews, rating, LQS, sellers, and history. It also specifies the no-marketplace failure behavior and the mandatory account-notice handling, so an agent has what it needs to invoke and interpret the tool correctly.

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 adds valuable semantics for marketplace: ask once, reuse for every later call, never assume the US, and money is in local currency. The ASIN parameter is already clear from the schema and needs no extra explanation.

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 explicitly states a specific verb and resource: 'Full raw data for a single Amazon product by ASIN' and enumerates the included fields. It also says 'Pure data fetch (no AI analysis)', which helps distinguish it from analysis-oriented siblings like amzscout_analyze_product_set.

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?

The description provides a detailed 'How to use' workflow—audit demand trend, pricing, competition, listing quality, then give a GO/NO-GO conclusion. It also gives clear guidance on asking once for a marketplace and reusing it, but it does not explicitly name alternative tools or state when not to use this tool.

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