Skip to main content
Glama

Nexscope Ecommerce Data MCP

Amazon Broad Product Search

nexscope_amazon_broad_product_search
Read-only

Use Nexscope data to search and filter Amazon products, supporting multi-dimensional criteria including price, monthly sales, BSR ranking, gross margin, ratings, fulfillment method, badges, seller origin, and more across multiple Amazon marketplaces. Trigger when the user mentions Amazon product selection research, product filtering, sales filtering, product discovery, BSR analysis, niche product discovery, competitor analysis, market opportunity assessment, product-level market size estimation, gross margin screening, Nexscope product selection, Amazon product selection, sales filtering, BSR analysis, profit screening, market analysis, product selection tool. Even if the user does not explicitly mention "Nexscope", if their need involves filtering and analyzing Amazon product-level data for product selection, this skill should also be triggered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nexscope_amazon_broad_product_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidNoUser ID, maxLength 1000
pageNoPage number, starting from 1, default 1
sizeNoResults per page (10-100), default 20. page * size must not exceed 2000.
orderNoOptional sort configuration. When supplied, both field and desc are required. Omit to sort by total_units descending.
chatIdNoChat ID, maxLength 1000
maxBsrNoHighest main category BSR rank
maxFbaNoMaximum FBA shipping fee (>= 0)
minBsrNoLowest main category BSR rank
minFbaNoMinimum FBA shipping fee (>= 0)
teamIdNoTeam ID, maxLength 1000
keywordNoSearch keyword; translate to the corresponding country's language whenever possible, e.g. use English keywords for the US, German keywords for Germany, etc.; maxLength 10240
maxPriceNoMaximum price (>= 0)
maxUnitsNoMaximum monthly sales volume (>= 0)
minPriceNoMinimum price (>= 0)
minUnitsNoMinimum monthly sales volume (>= 0)
matchTypeNoMatch type: 1 = phrase match (default), 2 = fuzzy match, 3 = exact match
maxProfitNoMaximum gross margin, unit % (1-100)
maxRatingNoMaximum rating value (0-5), 3.8-4.3 is the product improvement opportunity range
minProfitNoMinimum gross margin, unit % (1-100)
minRatingNoMinimum rating value (0-5)
nodeLabelNoAmazon category name; maxLength 1000
requestIdNoPush ID, maxLength 1000
maxAmzUnitNoMaximum variant last-30-day sales volume (only supported for last 30 days queries); minimum 0
maxRatingsNoMaximum review count (0-10000)
maxRevenueNoMaximum monthly sales revenue (>= 0)
maxSellersNoMaximum number of sellers
maxWeightsNoMaximum weight (>= 0)
minAmzUnitNoMinimum variant last-30-day sales volume (only supported when dataSnapshotMonth is a "last 30 days" type query); minimum 0
minRatingsNoMinimum review count (0-10000)
minRevenueNoMinimum monthly sales revenue (>= 0)
minSellersNoMinimum number of sellers
minWeightsNoMinimum weight (>= 0)
nodeIdPathNoAmazon category node ID; maxLength 1000
order.descNoRequired with order. Use the string "true" for descending or "false" for ascending.
weightUnitNoWeight unit: g, kg, oz, lb. This field must be specified if the parameters include weight filtering
fulfillmentNoFulfillment method: single select AMZ / FBA / FBM, or multi-select such as AMZ,FBA, FBA,FBM, AMZ,FBA,FBM, etc.; multiple conditions use comma separation; empty means no limit
marketplaceNoMarketplace site code, default US. Only US, UK, DE, FR, JP, CA, IT, ES, MX, IN are allowed (must match this enum; AU, TR, and other unlisted sites are not supported)
order.fieldNoRequired with order. Sort field: total_units, total_amount, bsr_rank, price, rating, reviews, profit, reviews_rate, available_date, questions, total_units_growth, total_amount_growth, reviews_increasement, bsr_rank_cv, bsr_rank_cr, amz_unit. An empty string disables business-field sorting.
sellerNationNoSeller location code (e.g. US, CN, HK), multiple conditions comma-separated, default no limit
dimensionTypeNoPackage dimension type (codes vary by site, see below)
excludeBrandsNoExclude brands; maxLength 10240
filterSubNodeNoWhether to filter subcategory nodes; only effective when nodeLabel or nodeIdPath has a value; pass JSON boolean true / false
includeBrandsNoInclude brands; maxLength 10240
maxVariationsNoMaximum number of variations
minVariationsNoMinimum number of variations
showVariationNoWhether to query variants: Y or N, default N
excludeSellersNoExclude sellers; maxLength 10240
includeSellersNoInclude sellers; maxLength 10240
badgeBestSellerNoBest Seller badge filter: Y, N, or empty (all)
badgeNewReleaseNoNew Release badge filter: Y, N, or empty (all)
excludeKeywordsNoExclude keywords; maxLength 10240
maxBsrGrowthRateNoMaximum BSR growth rate, unit %
minBsrGrowthRateNoMinimum BSR growth rate, unit %
dataSnapshotMonthNoProduct data snapshot month, format yyyyMM (e.g. 202412 for December 2024 data snapshot), or nearly for last 30 days real-time data. Default: nearly. Used for historical analysis and period comparison; only supports existing historical snapshots, future dates are not supported; maxLength 1000
maxBsrGrowthCountNoMaximum main category BSR growth count
maxSubNodeBsrRankNoHighest subcategory BSR rank (requires filterSubNode = true)
minBsrGrowthCountNoMinimum BSR growth count
minSubNodeBsrRankNoLowest subcategory BSR rank (requires filterSubNode = true)
badgeAmazonsChoiceNoAmazon's Choice badge filter: Y, N, or empty (all)
maxUnitsGrowthRateNoMaximum monthly sales volume growth rate, unit %
minUnitsGrowthRateNoMinimum monthly sales volume growth rate, unit %
hideUnlistedProductNoWhether to hide delisted products, default true
maxRatingsGrowthCountNoMaximum monthly new review count (>= 0)
minRatingsGrowthCountNoMinimum monthly new review count (>= 0)
listedWithinLastMonthsNoTime since listing (months), only allowed: 1, 3, 6, 12, 24 (must match these enum values; do not pass other integers)
maxListingQualityScoreNoMaximum Listing page quality score (>= 0)
minListingQualityScoreNoMinimum Listing page quality score (>= 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / order / description
      Previous value: -"Sort configuration; if passed, it is recommended to provide both field and desc (both are required in the sub-schema)"New value: +"Optional sort configuration. When supplied, both field and desc are required. Omit to sort by total_units descending."
    • changedInput schema / properties / order.desc / description
      Previous value: -"\"true\" descending, \"false\" ascending; default \"true\"; maxLength 1000"New value: +"Required with order. Use the string \"true\" for descending or \"false\" for ascending."
    • changedInput schema / properties / order.field / description
      Previous value: -"Sort field: total_units (monthly sales), total_amount (monthly revenue), bsr_rank, price, rating, reviews, profit, reviews_rate, available_date, questions, total_units_growth, total_amount_growth, reviews_increasement, bsr_rank_cv, bsr_rank_cr, amz_unit (variant sales). Default total_units. Pass an empty string \"\" to not sort by the above business fields (full query sort semantics are handled by the server)"New value: +"Required with order. Sort field: total_units, total_amount, bsr_rank, price, rating, reviews, profit, reviews_rate, available_date, questions, total_units_growth, total_amount_growth, reviews_increasement, bsr_rank_cv, bsr_rank_cr, amz_unit. An empty string disables business-field sorting."
    • changedInput schema / properties / size / description
      Previous value: -"Results per page (10-100), default 20"New value: +"Results per page (10-100), default 20. page * size must not exceed 2000."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description confirms read-style analysis but omits behavioral facts it could cheaply add, such as the page*size <= 2000 retrieval ceiling, the default 'nearly' (last-30-days) snapshot, and the default sort by total_units descending, all of which materially affect how results come back.

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 first sentence is well front-loaded and informative, but the second is a keyword dump that repeats 'BSR analysis', 'sales filtering', and 'product selection' multiple times and mixes noun phrases with trigger conditions in one run-on. Substantial length is spent restating the same trigger idea rather than adding new information.

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?

For a 67-parameter, all-optional read-only search tool with no output schema, the description conveys the domain, scope, and filter breadth adequately, and the schema covers every parameter. What is missing is guidance on pagination limits and snapshot defaults, which is a modest gap rather than a blocking one.

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?

With 100% schema description coverage across 67 parameters, the schema already carries the semantics and the baseline is 3. The description does add value by grouping the criteria into recognizable categories (price, sales, BSR, margin, ratings, fulfillment, badges, seller origin) that help an agent navigate the parameter set, but it introduces no syntax, default, or interaction rules beyond what the schema states.

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 opening sentence names a specific verb (search and filter) and resource (Amazon products) and enumerates the filterable dimensions (price, sales, BSR, margin, ratings, fulfillment, badges, seller origin) across marketplaces. It is clear what the tool does, but it never distinguishes itself from near-identical siblings such as nexscope_amazon_market_product_search, nexscope_amazon_product_database_search, or nexscope_amazon_product_discovery.

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

Usage Guidelines3/5

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

The description supplies a long list of trigger scenarios (product selection research, BSR analysis, niche discovery, margin screening) and even says to trigger when 'Nexscope' is not mentioned, which gives ample positive context. However, there is no guidance on when NOT to use it or which sibling to prefer for overlapping jobs like database search or product discovery, so an agent facing seven similar Amazon search tools still has to guess.

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.

Resources