Skip to main content
Glama
ncosic

Webotee Amazon Product Research

operator_buybox_losses

Read-only

Find ASINs where a seller loses the buy box, ranked by recoverable revenue at risk, with suggested repricing actions to win back the box.

Instructions

For ONE operator (seller), find the ASINs where it's losing the buy-box — it carries the listing but holds less than max_buybox_share_pct of the buy-box — ranked by estimated 30-day revenue at risk. Each leak returns who's winning the box, the operator's vs the winner's sanitized price and the gap, how many sellers are on the listing, a situation (price_gap | tied_price | amazon_in_box | reseller_swarm), a suggested_action (reprice_to_win | enable_fba | defend_match_only | evaluate_or_exit), and a suggested_target_price when the box is winnable on price. Totals include the recoverable price-gap-only revenue. Use when the user asks 'where is seller X losing the buy-box', 'X's buy-box leaks', 'which ASINs should X reprice', 'where is X leaving money on the table', or 'what's X's revenue at risk'. Sortable by revenue-at-risk (default), price gap, buy-box share, or listing revenue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operator_nameYesSeller/operator name.
marketplace_idNo1 = Amazon UK, 2 = Amazon US (default).
max_buybox_share_pctNoOnly ASINs where the operator holds LESS than this share of the buy-box (0-1; default 0.75 — i.e. it's not dominating).
min_est_revenue_30dNoOnly ASINs with estimated 30-day listing revenue >= this.
min_priceNoOnly ASINs whose listing price >= this (skip pennies).
limitNoLeaks to return (default 25, max 100). This tool pages.
sortNoSort the leaks: revenue_at_risk (default), price_gap_pct (biggest recoverable gap), buybox_share (lowest first), or listing_revenue.
situation_inNoComma-separated situations to keep (price_gap, tied_price, amazon_in_box, reseller_swarm).
exclude_amazon_in_boxNoDrop ASINs where Amazon holds the box (you can't win those).
fulfillment_inNoComma-separated operator fulfillment to keep (FBA, FBM).
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description adds rich behavioral details: output structure with fields like situation, suggested_action, totals, pagination note, and sorting options. It does not contradict annotations, though it could mention authorization requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and concise despite its length. It is front-loaded with the core purpose, then details output, usage examples, and sorting/filtering without redundancy. 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 10 parameters, no output schema, and no nested objects, the description thoroughly covers all aspects: required parameters, optional filters, output fields, and sort options. It leaves no ambiguity for an agent to understand input and expected output.

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%, and the description adds contextual meaning beyond schemas, e.g., explaining max_buybox_share_pct's default as 'not dominating' and how situation_in is a comma-separated list. This enhances usability.

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 finds ASINs where a specific seller is losing the buy-box, ranked by revenue at risk. It includes specific verbs ('find', 'returns') and distinguishes from siblings like 'asin_buybox_history' by focusing on a single operator's losses with actionable suggestions.

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 queries ('where is seller X losing the buy-box', etc.), giving clear guidance on when to use the tool. However, it does not explicitly state when not to use it or mention alternative tools.

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