AMZScout Skill + MCP

Extra catalog facts about one Amazon ASIN that amzscout_analyze_product does not include: bullet features, materials, included components, ingredients, hazmat info, UPCs and manufacturer; on request also frequently-bought-together / bundle ASINs, listing videos, return rate, brand store link and buy box seller history. No sales, price or review numbers — those come from amzscout_analyze_product. Pure data fetch (no AI analysis). When to call: together with amzscout_analyze_product whenever the user asks about one specific product (same ASIN and marketplace), so the answer carries the listing facts as well as the numbers. Call WITHOUT sections by default (returns catalog + identifiers); add relations / media / buybox only when the question is about them. How to use: describe what the product actually is and how it is positioned — key features, materials, what is in the box, compliance flags (hazmat, ingredients) — and point out what a competing listing would need to match or beat. Present facts as written on the listing; do not invent missing ones. 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.

Market snapshot for an Amazon niche/keyword — top products by revenue plus computed aggregates (price/sales/revenue/review distributions, revenue concentration, brand spread). Pure data fetch (no AI analysis) — reason over the returned data yourself. How to use: judge niche attractiveness — demand concentration (revenueTop5SharePercent: high = winner-takes-all, low = fragmented/open), price bands and where the money sits, review counts as entry moats, brand dominance vs no-name spread, and standout products (high sales + weak rating/reviews = displacement opportunity). 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.

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). Listing facts (features, materials, ingredients, UPC, videos) are NOT here — they come from amzscout_advanced_product_data (call both for the same ASIN). 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.

Raw data across an explicit set of 2–100 ASINs — product rows plus computed aggregates (price/sales/revenue/review distributions, revenue concentration, brand spread). Pure data fetch (no AI analysis) — reason over the returned data yourself. To discover products from a keyword instead, analyzeNiche is the equivalent. How to use: treat the set as a mini-market — segment products into groups, spot where demand concentrates, flag outliers (price, sales, review anomalies), and summarize group-level signals. 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.

Raw head-to-head data for 2–5 Amazon niches / category keywords — per-niche product sets plus computed aggregates (price/sales/revenue distributions, revenue concentration, brand spread). Pure data fetch (no AI analysis) — do the comparison yourself. For ASINs, compareProducts is the equivalent. How to use: weigh demand (total est. revenue/sales) against competition (review levels, brand concentration) and price levels per niche, then give a verdict on which niche is the better opportunity for a new seller and under what conditions. 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.

Side-by-side raw data for 2–5 Amazon products by ASIN — price, sales/revenue estimates, reviews, listing quality, plus history when available. Pure data fetch (no AI analysis) — do the comparison yourself. For a single ASIN, analyzeProduct is the equivalent. How to use: compare demand (est. sales), revenue, review moat and rating, price positioning, listing quality, and history trends (growing vs declining), then give a verdict on which product is the stronger opportunity and why. 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.

Start AMZScout: returns a welcome message and the example questions the user can try. Call this at the very START of the conversation, and whenever the user greets you or says things like "Ask AMZScout" (case-insensitive — "ask amzscout", "ASK AMZSCOUT" and any other capitalization all count), "demo", "begin", "hello", "help", or "what can you do". Relay its output verbatim.

List products under a specific Amazon brand. Pre-validates the brand name via cached AI check, then filters keyword-search results to rows whose brand field actually matches. On no-match, returns the brands that did appear in the keyword pool so callers can suggest alternatives. How to use: assess the brand's Amazon footprint — lineup breadth, price range, which products carry the revenue, and how strong its review moat is. 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.

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.

Find which Amazon marketplaces list an ASIN, and get its product link on every marketplace (amazon.com, .co.uk, .de, .fr, .it, .es, .ca, .com.mx, .com.br, .in, .co.jp, .com.au, .ae, .sa). For each marketplace where it is listed: title, price in that marketplace's local currency, estimated monthly sales. Paid: 1 000 tokens per marketplace checked, per ASIN (14 000 per ASIN). How to use: call it ONLY when the user asks where / on which Amazon marketplaces a product is sold, or wants its links on other marketplaces. Do NOT call it just to choose a marketplace for analysis — for that, ask the user once which marketplace they work on and reuse it for the whole conversation. Present the result as a list (country, link, local price, sales); if the user then wants analysis, pass the marketplace they pick to amzscout_analyze_product / amzscout_get_keywords. 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.

Given a user use-case, returns the AMZScout tools & Sellerhook services catalog (with tracking links) so you can recommend the right AMZScout product/feature. Use for "which AMZScout tool should I use for X" questions. 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.

Buy box, competing offers and price/rank statistics for one Amazon ASIN — who owns the buy box and at what price, how ownership has split between sellers, FBA vs FBM offer counts, the live offer list with seller names and ratings, price levels over 30/90/180/365 days with all-time extremes, sales-rank drops, out-of-stock share, and buy box ownership history. Built for reseller / online-arbitrage questions, not private-label research — for demand and revenue estimates use analyzeProduct instead. Pure data fetch (no AI analysis). IMPORTANT: call it first WITHOUT sections — the summary alone answers most questions, and the reply lists which sections hold data for this ASIN. Only request sections when the summary is not enough; asking for all six returns several KB of detail you will rarely need. How to use: judge whether the listing is worth reselling — Amazon in the buy box or a single seller holding most of it means little room, many FBA offers means price competition, high out-of-stock share means supply gaps you could fill, and rank drops indicate how fast it sells. 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.

TF-IDF search across the AMZScout knowledge base (Amazon-seller tutorials, brand reference, glossary). Returns the top-K relevant chunks with title, source URL and text. Use this to ground answers in factual material. 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.

Keyword search against Amazon — returns the top N products with price, sales, revenue, reviews, rating. Pure data fetch (no AI analysis). Best when you need raw product rows (specific sort order or filters); analyzeNiche additionally returns computed market aggregates on top of the rows. How to use: scan the rows for demand leaders, price clusters, and low-review listings that still sell — those are the entry-opportunity signals. 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.

The caller's AMZScout AI-agents token balance — remaining, used, and limit. Free — no tokens are charged for this call. How to use: answer "how many tokens do I have left", "what's my usage / balance / limit", or when a call fails on quota. Report the remaining figure first. 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.