Skip to main content
Glama
ncosic

Webotee Amazon Product Research

operator_top_asins

Read-only

Retrieve ASINs where a seller or operator most frequently wins the Buy Box, ranked by estimated 30-day sales. Shows each ASIN's operator-specific sales estimates and Buy Box share.

Instructions

Show the ASINs an operator wins the buybox on most often, ranked by ESTIMATED 30-day sales by default. For each ASIN it returns the operator's estimated units sold and revenue in the last 30 days (est_units_30d, est_revenue_30d — the product's sales estimate weighted by the operator's buy-box share) plus the operator's BUYBOX SHARE (percent of observed days it held the buybox; normalized, not raw days). Sortable by est_sales (default), observed buybox days won, price, or days seen. Use when the user asks 'what ASINs does this seller win on', 'top ASINs for operator X', 'what does this seller sell the most of', 'best products for this seller', or any ASIN-level operator drill-down. Each ASIN also carries product brand, title, and price (or price range) plus its fulfillment (FBA/FBM/AMZ + amz/fba pct).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operator_nameYesSeller/operator name.
sortNoSort order: est_sales (estimated 30-day revenue, default), buybox_days (observed buybox days won), price, or days_seen.
marketplace_idNo1 = Amazon UK, 2 = Amazon US (default)
limitNoNumber of ASINs to return (default 10, max 50).
min_buybox_share_pctNoOnly ASINs where the operator's buybox share >= this.
max_buybox_share_pctNo
min_observed_buybox_daysNo
max_observed_buybox_daysNo
min_days_seenNo
max_days_seenNo
min_est_units_30dNo
max_est_units_30dNo
min_est_revenue_30dNo
max_est_revenue_30dNo
min_buybox_avg_priceNo
max_buybox_avg_priceNo
est_basis_inNoComma-separated sales-estimate sources to keep.
asinNoExact ASIN match.
asin_containsNo
first_seen_fromNoYYYY-MM-DD.
first_seen_toNo
last_seen_fromNo
last_seen_toNo
product_brandNoExact product brand (case-insensitive).
product_brand_containsNo
product_title_containsNo
min_priceNo
max_priceNo
fulfillment_inNoComma-separated FBA/FBM/AMZ to keep.
min_fulfillment_amz_dom_pctNo
max_fulfillment_amz_dom_pctNo
min_fulfillment_fba_pen_pctNo
max_fulfillment_fba_pen_pctNo
Behavior4/5

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

Annotations already indicate readOnlyHint=true. The description adds behavioral context beyond annotations by explaining that returned metrics like est_units_30d and est_revenue_30d are weighted by buybox share, and buybox share is normalized. This adds value without contradicting 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 relatively long but well-structured, starting with main functionality, then defining metrics, then usage examples. It could be slightly more concise, but every sentence adds value.

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?

Given the complexity (33 parameters, no output schema), the description thoroughly explains the tool's purpose, returned metrics, sorting, and typical use cases. It provides a complete picture for an agent to select and invoke this 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 only 30%, but the description adds meaning for key parameters: it explains the meaning of est_units_30d, est_revenue_30d, and buybox share. It also clarifies sort options. While many filtering parameters remain minimally described, the description compensates for the low coverage with essential context.

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 it shows ASINs an operator wins the buybox on most often, ranked by estimated 30-day sales. It provides specific example queries for user intent. This distinguishes it from sibling tools that focus on other aspects like brand analysis or category metrics.

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 explicit example phrases like 'what ASINs does this seller win on' and 'top ASINs for operator X'. However, it does not specify when not to use this tool or suggest alternative tools for different contexts.

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