Skip to main content
Glama

Amazon ABA & Business Insights: opportunity/search By Metrics API

nexscope_data_amazon_opportunity_search_by_metrics
Read-only

Amazon ABA & Business Insights: opportunity/search By Metrics API.

Input Schema

NameRequiredDescriptionDefault
limitNoReturns the upper limit of the number of items; without the `page` parameter, the most recent N items are returned in reverse order of collection time.
keywordNoSearch keyword text fragments (LIKE fuzzy matching).
nicheNameNoTrack normalized name fragment (LIKE, snake_case lowercase), suitable for track timing comparison.
amazonDomainNoAmazon site code (closed enumeration), currently only supports `US`; if not specified, only the US site will be checked by default.
priceMaxUsdGteNoThe track’s maximum product price limit (USD).
priceMaxUsdLteNoThe track’s maximum product price limit (USD).
priceMinUsdGteNoThe lowest product price limit on the track (USD).
priceMinUsdLteNoThe track’s minimum product price limit (USD).
nichePeakMonthGteNoSearch peak month lower limit.
nichePeakMonthLteNoSearch peak month cap.
demoGenderDominantNoGender dominant (closed enumeration): `female` / `male` / `mixed` / `unspecified`.
nicheBrandCountGteNoMinimum number of active brands.
nicheBrandCountLteNoMaximum number of active brands.
demoPrimaryAgeMaxGteNoThe minimum value of the upper bound of the age of the main population.
demoPrimaryAgeMaxLteNoThe maximum value of the upper bound of the age of the host group.
demoPrimaryAgeMinGteNoThe minimum value of the lower bound of the age of the main population.
demoPrimaryAgeMinLteNoThe maximum value of the lower bound of the age of the host group.
demoPrimaryIncomeTierNoIncome file (closed enumeration): `low` / `middle_low` / `middle` / `middle_upper` / `upper_middle` / `high`.
priceSweetSpotMaxUsdGteNoLower bound of Sweet Spot upper limit (USD).
priceSweetSpotMaxUsdLteNoThe upper bound of the Sweet Spot limit (USD).
priceSweetSpotMinUsdGteNoThe lower bound of the Sweet Spot lower limit (USD).
priceSweetSpotMinUsdLteNoThe upper bound of the Sweet Spot lower limit (USD).
reviewNegativeTop1TopicNoNegative review #1 topic snippet (snake_case, LIKE), such as `size`, `quality`, `durability`.
reviewNegativeTop2TopicNoNegative review #2 topic snippet (snake_case, LIKE).
reviewPositiveTop1TopicNoLike #1 theme snippets (snake_case, LIKE), such as `comfort`, `quality_overall_generic`.
searchTopCategory1LabelNoSearch traffic first type target tag fragment (snake_case, LIKE), such as `core_product_terms`, `set_kit_configurations`.
featureTopBrandsContainsNoTop 3 brand name fragments (original text LIKE, case sensitive).
demoLifeStageTagsContainsNoLife stage tag fragment (snake_case, LIKE), such as `parent`, `student`, `retiree`, `athlete`.
nichePeakSearchVolumeAtLeastGteNoLower bound for peak monthly search volume.
nichePeakSearchVolumeAtLeastLteNoThe upper bound of peak monthly search volume.
priceMidClickSharePctAtLeastGteNoMid-range click share floor.
priceMidClickSharePctAtLeastLteNoMid-range click share cap.
reviewNegativeTop1PctAtLeastGteNoThe lower limit of negative review #1 topic proportion (proportion of negative reviews).
reviewNegativeTop1PctAtLeastLteNoThe upper limit for the proportion of negative review #1 topics.
reviewPositiveTop1PctAtLeastGteNoThe lower limit of the proportion of positive #1 topics (the proportion of positive comments).
reviewPositiveTop1PctAtLeastLteNoThe upper limit of the proportion of positive #1 topics.
featureEmergingTrendTagsContainsNoEmerging trend feature tag fragments (snake_case, LIKE), such as `cordless`, `portable`, `smart`.
nicheRevenue360dMaxUsdAtLeastGteNoThe minimum value of the 360-day market revenue upper bound (USD).
nicheRevenue360dMaxUsdAtLeastLteNoThe maximum value of the 360-day market revenue upper bound (USD).
nicheRevenue360dMinUsdAtLeastGteNoThe minimum value of the 360-day market revenue lower bound (USD).
nicheRevenue360dMinUsdAtLeastLteNoThe maximum value of the 360-day market revenue lower bound (USD).
priceHighClickSharePctAtLeastGteNoThe lower limit of click share for high-end products.
priceHighClickSharePctAtLeastLteNoHigh-end click share limit.
priceEntryClickSharePctAtLeastGteNoMinimum click share for entry-level users.
priceEntryClickSharePctAtLeastLteNoThe entry level click share limit.
featureNewAvgReviewCountAtLeastGteNoThe lower limit for the average number of reviews for new products.
featureNewAvgReviewCountAtLeastLteNoThe upper limit of the average number of reviews for new products.
featureTop5BrandSharePctAtLeastGteNoThe lower limit of the total share of the top 5 brands.
featureTop5BrandSharePctAtLeastLteNoThe upper limit of the total share of the top 5 brands.
featureUncommonFeatureTagsContainsNoRare differentiation feature tag fragments (snake_case, LIKE), such as `hema_free`, `medical_grade_silicone`.
reviewStrategicInsightTagsContainsNoComment policy suggests tag snippets (snake_case, LIKE), such as `sizing_clarity`, `material_transparency`.
nicheBrandCountYoyChangePctAtLeastGteNoThe lower limit of the year-on-year change rate of the number of brands (%, with sign).
nicheBrandCountYoyChangePctAtLeastLteNoThe upper limit of the year-on-year change rate of the number of brands (%, with sign).
nicheSearchVolumeYoyChangePctAtLeastGteNoThe lower limit of the year-on-year change rate of search volume (%, signed).
nicheSearchVolumeYoyChangePctAtLeastLteNoThe upper limit of the year-over-year change rate of search volume (%, signed).
nicheTop5ProductClickSharePctAtLeastGteNoThe lower limit for the click share of the top 5 products.
nicheTop5ProductClickSharePctAtLeastLteNoThe upper limit of the click share of the top 5 products.
featureEstablishedAvgReviewCountAtLeastGteNoThe lower limit of the average number of comments for mature and old products.
featureEstablishedAvgReviewCountAtLeastLteNoThe upper limit of the average number of comments for mature and old products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no statement of result shape, whether results are ranked/sorted, pagination behavior for the 'limit'/'page' interaction, or cost/latency of a 59-filter query. With a mutation-free read tool, this is a missed opportunity rather than a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short, but the brevity is under-specification rather than conciseness: a single title-echoing fragment with no front-loaded statement of action or outcome. Nothing is wasted, but nothing useful is delivered either.

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?

This is a high-complexity tool with 59 parameters, no required fields, no output schema, and no annotations covering return semantics. The description should at minimum explain what a 'metrics-based opportunity search' returns and what the default (unfiltered) behavior is; instead it says nothing, leaving the agent unable to predict results from a zero-filter call.

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

Parameters3/5

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

Schema description coverage is 100% with all 59 parameters individually documented, so the schema carries the semantic load and the baseline is 3. The description contributes no additional meaning, such as how the many min/max (Gte/Lte) filter pairs are intended to be combined or which subset matters most.

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

Purpose2/5

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

The description restates the title verbatim: 'Amazon ABA & Business Insights: opportunity/search By Metrics API.' It identifies the domain (Amazon ABA/Business Insights) and the endpoint family (opportunity search by metrics) but contains no verb describing what the tool actually does or returns, so it is effectively tautological against the name.

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

Usage Guidelines1/5

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

There is no indication of when to use this tool, what problem it solves, or how it differs from the very close sibling nexscope_amazon_opportunity_report_by_keyword (and nexscope_amazon_niche_info_by_keyword). An agent has no basis in the description for choosing this over its siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.