Skip to main content
Glama
ncosic

Webotee Amazon Product Research

buybox_loss_alert

Read-only

Identify ASINs where your brand lost the buy box to unauthorized sellers, prioritized by estimated revenue at stake, to recover sales.

Instructions

Find the ASINs where a brand you own has LOST the buy box to a seller outside your authorized list — ranked by estimated revenue at stake — so you can act on the costliest first. Each flagged ASIN carries its product brand, title and price (or price range) plus its fulfillment (FBA/FBM/AMZ). Save your authorized list first (authorized_seller_set) for precise flagging; without it, ASINs where a third-party operator holds the buy box are flagged. Use when the user asks 'where am I losing the buy box on ', 'buy-box loss on my ASINs', 'which of my listings did I lose'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYesThe brand you own/manage.
authorized_sellersNoOptional. Your authorized sellers (else the saved list is used).
marketplace_idNo1 = Amazon UK, 2 = Amazon US (default)
limitNo
asinNoExact ASIN match.
asin_containsNo
buybox_holderNoExact current buy-box holder (case-insensitive).
buybox_holder_containsNo
min_observed_buybox_daysNo
max_observed_buybox_daysNo
min_est_units_30dNo
max_est_units_30dNo
min_buybox_priceNo
max_buybox_priceNo
min_est_revenue_at_stake_30dNo
max_est_revenue_at_stake_30dNo
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 declare readOnlyHint=true, and description adds that results are ranked by revenue, includes product brand/title/price/fulfillment. Describes fallback behavior when no authorized list set. No contradiction.

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?

Description is front-loaded with purpose, then output details, then prerequisite and examples. Slightly verbose but well-structured.

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 26 parameters and no output schema, the description adequately covers the core function, output fields, and prerequisite. Does not explain all filter combinations but sufficient for an alert tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 27%, but description does not explain any parameters beyond what is already in the schema. It mentions the 'brand' parameter implicitly but does not add detail for the many filter parameters.

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 uses specific verbs ('Find') and clearly states the resource (ASINs where brand lost buy box), ranking by revenue at stake. It differentiates from siblings like authorized_seller_set and operator_buybox_losses by focusing on brand-owned ASINs and requiring authorized list.

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?

Provides explicit example queries ('where am I losing the buy box') and mentions prerequisite (save authorized list). Lacks explicit when-not-to-use, but context is clear.

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