Skip to main content
Glama
ncosic

Webotee Amazon Product Research

watchlist_stats

Read-only

Retrieve a bulk report of Amazon stats for your entire sourcing watchlist in one call. Get composite scores, seller counts, buy-box shares, and fulfillment data for every tracked ASIN.

Instructions

BULK report of key Amazon stats for the user's WHOLE watchlist in ONE call — every tracked ASIN in the workspace's sourcing watchlist for a marketplace, in a single pass. Use this report instead of looping a per-ASIN tool over the whole watchlist. Each tracked ASIN returns its composite sourcing score, distinct seller count, buy-box leader share, fulfillment (FBA/FBM/AMZ with amz/fba pct), product brand/title and price (or price range). Also returns a top-level summary across the whole watchlist (tracked total, scored count, average score, score buckets, Amazon-dominant / FBA-dominant counts, single-seller vs high-competition counts). Use when the user asks 'show stats for my whole watchlist', 'summarize my watchlist', 'which of my tracked ASINs are single-seller / Amazon-dominant / high-competition', 'score distribution of my watchlist', or any bulk watchlist overview. One call covers the entire watchlist — do NOT call a per-ASIN tool in a loop.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketplace_idNoMarketplace to scope to: 1 = Amazon UK, 2 = Amazon US (default), 3 = Walmart US. One marketplace per call.
sortNoSort order (all descending): score (composite sourcing score, default), seller_count (distinct sellers), buybox_share (buy-box leader share), amz_dominance, fba_penetration, or price.
limitNo
min_composite_scoreNoOnly tracked ASINs with composite sourcing score >= this.
max_composite_scoreNo
min_seller_countNoOnly ASINs with >= this many distinct sellers.
max_seller_countNo
min_buybox_share_pctNoOnly ASINs where the buy-box leader's share >= this percent.
max_buybox_share_pctNo
min_amz_dominance_pctNoOnly ASINs with Amazon buy-box dominance >= this percent.
max_amz_dominance_pctNo
min_fba_penetration_pctNoOnly ASINs with FBA penetration >= this percent.
max_fba_penetration_pctNo
min_priceNo
max_priceNo
fulfillment_inNoComma-separated FBA/FBM/AMZ to keep.
product_brandNoExact product brand (case-insensitive).
product_brand_containsNo
asinNoExact ASIN match.
asin_containsNo
Behavior4/5

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

Annotations already set readOnlyHint=true. The description adds detail on return values (per-ASIN fields and top-level summary) and confirms no side effects. It does not contradict 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 front-loaded with the key purpose, then logically structured with return details and example uses. While verbose, every sentence adds value and it remains focused.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 20 parameters and no output schema, the description adequately explains the tool's output (per-ASIN fields and summary). It could specify the exact return structure, but the provided information is sufficient for agent understanding.

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 description coverage is 50%, so the schema partially documents parameters. The description does not add parameter-specific details beyond the schema. It provides overall context but doesn't compensate for the undocumented half.

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 clearly states the tool's purpose: a bulk report of key Amazon stats for the user's entire watchlist in one call. It uses strong verbs like 'BULK report' and explicitly distinguishes from per-ASIN tools, preventing looping.

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 clear when-to-use guidance, explicitly advising against looping per-ASIN tools and listing example queries. It does not explicitly mention when not to use it, but the context is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ncosic/webotee-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server