Skip to main content
Glama
ncosic

Webotee Amazon Product Research

find_new_operators

Read-only

Find sellers newly observed selling on Amazon within a time window. Filters by brands, ASINs, and FBA share to surface emerging operators.

Instructions

Find operators (sellers) we FIRST OBSERVED selling recently — their earliest observation in our data falls in the window. An observation signal, NOT confirmed market entry: sparse sampling can surface a long-present seller the first time we see them. Different from top_expanding_operators (existing operators adding brands). Use when the user asks 'new sellers this month', 'who just started selling', 'newly seen operators', or any question about emerging/newly-observed sellers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
since_daysNoHow far back to look (default 30, max 180).
min_brandsNoMinimum brands to filter out trivial sellers (default 5).
marketplace_idNo1 = Amazon UK, 2 = Amazon US (default)
limitNo
seller_nameNoExact seller name (case-insensitive).
seller_name_containsNo
earliest_seen_fromNoYYYY-MM-DD lower bound on earliest-seen date.
earliest_seen_toNo
min_total_asinsNo
max_total_asinsNo
min_total_observed_buybox_daysNo
max_total_observed_buybox_daysNo
min_operator_fba_share_pctNo
max_operator_fba_share_pctNo
min_avg_ratingNo
max_avg_ratingNo
min_avg_rating_countNo
max_avg_rating_countNo
Behavior5/5

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

Beyond the readOnlyHint annotation, the description explains that this is an 'observation signal, NOT confirmed market entry' and warns that 'sparse sampling can surface a long-present seller the first time we see them', which adds crucial behavioral context.

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 two sentences plus a usage note, front-loaded with the core concept and differentiation, with no wasted words.

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?

While the description excels at explaining the tool's purpose and usage, it does not address the 18 parameters or output format. Given the complexity (many parameters, no output schema), the description could be more complete for an AI agent to use effectively.

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 description coverage is only 28% (5 of 18 parameters have descriptions), and the tool description itself provides no additional parameter explanations. Many parameters remain undocumented, leaving the agent with insufficient semantic understanding to set them correctly.

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 verb+resource ('Find operators we FIRST OBSERVED selling recently') and clearly distinguishes from the sibling tool top_expanding_operators by stating it's for newly-observed sellers, not existing operators adding brands.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides example queries ('new sellers this month', 'who just started selling', 'newly seen operators') and explains the key difference from top_expanding_operators, giving clear guidance on when to use this tool.

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