Skip to main content
Glama
ncosic

Webotee Amazon Product Research

evaluate_brand

Read-only

Evaluate a brand's sales posture, distribution, and product performance to determine portfolio inclusion. Get metrics like revenue, churn rate, and top ASINs.

Instructions

Evaluate a brand for portfolio inclusion. Returns brand-level control posture, winner diversity (HHI), Amazon retail dominance %, FBA penetration %, catalog churn rate, total bought-past-month volume, estimated 30-day revenue, avg ship-by days, cross-brand operator count, plus the top 10 ASINs by composite sourcing score (each with product brand, title, price or price range, and fulfillment FBA/FBM/AMZ + amz/fba pct). Use when the user names a brand and asks 'is this worth carrying?', 'how does this brand look?', 'what is the churn rate?', or 'how fast does this brand ship?'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYesBrand name (case-insensitive).
marketplace_idNo1 = Amazon UK, 2 = Amazon US (default)
distribution_verdict_inNoComma-separated distribution verdicts to keep, e.g. 'DOMINANT SELLER', 'OPEN DISTRIBUTION', 'HIGH BRAND HEAT'. If the brand's verdict isn't in the list, an empty result is returned.
asinNoKeep only this ASIN in top_asins.
asin_containsNo
min_composite_scoreNo
max_composite_scoreNo
min_velocityNo
max_velocityNo
min_gatingNo
max_gatingNo
min_marginNo
max_marginNo
min_ratingNo
max_ratingNo
min_number_of_ratingsNo
max_number_of_ratingsNo
product_brandNoExact product brand (case-insensitive) on top_asins.
product_brand_containsNo
product_title_containsNo
min_priceNo
max_priceNo
fulfillment_inNoComma-separated FBA/FBM/AMZ to keep on top_asins.
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 the description details the output (control posture, HHI, etc.) beyond annotations. Doesn't mention error handling or rate limits, but sufficient for a read-only tool.

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?

The description is front-loaded with the main purpose and uses three sentences to cover key points. It could be slightly more structured (e.g., separating output list from usage), but is efficient and not verbose.

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?

Despite lacking an output schema, the description explains the return structure (brand-level metrics and top 10 ASINs with details) comprehensively. For a tool with 27 params, it covers the essentials, though parameter explanations are missing.

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 22%, yet the description does not elaborate on parameter meanings beyond the schema. Most parameters (e.g., min_composite_score, max_velocity) are left unexplained, failing to compensate for low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Evaluate a brand for portfolio inclusion' and lists specific metrics returned, making the purpose distinct. However, it does not explicitly differentiate from sibling tools like 'brand_similar' or 'brand_buybox_trajectory', so it's not a 5.

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 concrete examples of user queries ('is this worth carrying?', 'how does this brand look?') that trigger this tool. Missing explicit exclusion guidance or alternatives, so not a 5.

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