Skip to main content
Glama
ncosic

Webotee Amazon Product Research

find_undercompeted_brands

Read-only

Identify brands with few sellers and strong sales history. Source products with proven demand and low competition.

Instructions

Find brands with low seller competition but real sales presence. The flagship sourcing discovery tool. Use when the user asks 'find brands with few sellers', 'low competition brands', 'undercompeted brands under $50', 'brands I could source with little competition', or any variant of 'find me something to sell'. Pass seed_brand when user mentions a reference brand ('brands like Ninja', 'low competition in the same category as OXO') to constrain results to the same root category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_sellersNoMaximum unique sellers (competition ceiling). Default 20.
min_sellersNoMinimum unique sellers (default 10). Drops single-seller / brand-owner-only 'PL junk' so results show proven multi-seller demand (the default 10–20 window: under-competed but real).
min_buybox_daysNoMinimum observed buybox days in last 3 months (sales floor). Default 30.
max_avg_priceNoMaximum average buybox price in USD. Omit for no price filter.
min_avg_priceNoMinimum average buybox price in USD. Omit for no price filter.
seed_brandNoReference brand to derive category from. Results stay in the same root category.
category_idNoFilter to a specific root category ID. Overrides seed_brand if both given.
include_catchallNoInclude reseller umbrella brands (PATIKIL, Uxcell, etc.). Default false.
limitNo
marketplace_idNo1 = Amazon UK, 2 = Amazon US (default)
brandNoExact brand match (case-insensitive).
brand_containsNo
min_asin_countNo
max_asin_countNo
min_control_scoreNo
max_control_scoreNo
min_velocity_90dNo
max_velocity_90dNo
Behavior5/5

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

The description is consistent with the readOnlyHint annotation, stating it is a discovery tool. It adds important behavioral context such as being the flagship tool, detailing the default seller window, seed_brand constraint, and include_catchall filter, which goes beyond the annotation's scope.

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 concise, using a single paragraph that front-loads the core purpose, then provides example queries and seed_brand usage. Every sentence adds value with no redundancy.

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

Completeness3/5

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

Given 18 parameters and no output schema, the description covers the main use case and seed_brand but does not describe the return format or results. It omits guidance on many parameters, which may leave the agent uncertain about the output. Slightly incomplete for a complex tool.

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?

The input schema descriptions for parameters like min_sellers and max_sellers are already detailed and provide semantic meaning. The tool description adds value by explaining the purpose and context, though it does not elaborate on most parameters individually. With 56% schema coverage, the description supplements rather than repeats.

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 brands with low seller competition but real sales presence, and is identified as the flagship sourcing discovery tool. It distinguishes from siblings by providing specific user query examples and positioning as the primary sourcing tool.

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 explicitly lists when to use the tool with example queries and gives guidance on using seed_brand. It does not explicitly state when not to use or mention alternatives, but the provided examples sufficiently guide appropriate usage.

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