Skip to main content
Glama
ncosic

Webotee Amazon Product Research

brand_similar

Read-only

Find brands similar to a given brand using filters like category, price tier, competition level, and seller metrics. Identify comparable brands for product research or niche analysis.

Instructions

Find brands similar to a given brand by category, price tier, and competition level. Use when the user asks 'brands like Nike', 'similar brands to source', 'show me comparable brands', 'what else is in this niche', or any cohort/lookalike question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYesReference brand name (case-insensitive).
marketplace_idNo1 = Amazon UK, 2 = Amazon US (default)
limitNo
min_seller_countNoOnly similar brands with at least this many unique sellers (3m).
max_seller_countNo
min_asin_countNo
max_asin_countNo
min_buybox_days_3mNo
max_buybox_days_3mNo
min_control_scoreNo
max_control_scoreNo
min_avg_priceNo
max_avg_priceNo
brand_containsNoOnly keep similar brands whose name contains this substring.
Behavior3/5

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

The description aligns with the readOnlyHint annotation, indicating a read operation, but adds no additional behavioral context such as rate limits or failure modes.

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 a single sentence plus a usage clause, very concise and front-loaded with key purpose and examples.

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

Completeness2/5

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

With 14 parameters, no output schema, and minimal parameter explanations, the description lacks completeness for effective agent use.

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 29%, and the description does not explain the majority of parameters. It only mentions category, price tier, and competition level, which are not explicit 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 clearly states 'Find brands similar to a given brand by category, price tier, and competition level' and provides explicit example queries, making purpose unambiguous. It distinguishes from sibling tools by focusing on brand lookalikes.

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 tells when to use it via example queries like 'brands like Nike', but does not mention when not to use or 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