Skip to main content
Glama

Nexscope Ecommerce Data MCP

Amazon Intelligence SS: product Search API

nexscope_data_ss_product_search

Amazon Intelligence SS: product Search API.

Input Schema

NameRequiredDescriptionDefault
uidNoUser id, maxLength 1000
pageNoPage number, starting from 1
sizeNoNumber of items per page, 10–100
orderNoSorting configuration; it is recommended to provide both `field` and `desc` when passing in
chatIdNoConversation id, maxLength 1000
maxBsrNoTop Category BSR Ranking
maxFbaNoMaximum FBA shipping fee (>= 0)
minBsrNoCategory BSR lowest ranking
minFbaNoMinimum FBA shipping (>= 0)
teamIdNoTeam id, maxLength 1000
keywordNoSearch keywords, it is recommended to use the target site language; maxLength 10240
maxPriceNoHighest price (>= 0)
maxUnitsNoHighest monthly sales (>= 0)
minPriceNolowest price (>= 0)
minUnitsNoMinimum monthly sales volume (>= 0)
matchTypeNoMatching method: `1` phrase matching, `2` fuzzy matching, `3` precise matching
maxProfitNoMaximum gross profit margin, unit % (1–100)
maxRatingNoHighest rating value (0–5)
minProfitNoMinimum gross profit margin, unit % (1–100)
minRatingNoLowest rating value (0–5)
nodeLabelNoAmazon category name; maxLength 1000
requestIdNoPush id, maxLength 1000
maxAmzUnitNoThe highest sub-body sales volume in the past 30 days; only the query in the past 30 days is supported, the minimum value is 0
maxRatingsNoMaximum number of ratings (0–10000)
maxRevenueNoHighest monthly sales (>= 0)
maxSellersNoMaximum number of sellers
maxWeightsNoMaximum weight (>= 0)
minAmzUnitNoMinimum sub-body sales volume in the past 30 days; only `dataSnapshotMonth` is supported for queries in the past 30 days, the minimum value is 0
minRatingsNoMinimum number of ratings (0–10000)
minRevenueNoMinimum monthly sales (>= 0)
minSellersNoMinimum number of sellers
minWeightsNoMinimum weight (>= 0)
nodeIdPathNoAmazon category node ID; maxLength 1000
weightUnitNoWeight unit: `g`, `kg`, `oz`, `lb`; must be specified when using weight filtering
fulfillmentNoDelivery method: `AMZ`, `FBA`, `FBM`, multiple values separated by English commas
marketplaceNoOnly `US`, `UK`, `DE`, `FR`, `JP`, `CA`, `IT`, `ES`, `MX`, `IN` allowedUS
sellerNationNoSeller's location code, multiple values separated by commas
dimensionTypeNoPackaging size type, please see the description below for each site code
excludeBrandsNoExclude brands; maxLength 10240
filterSubNodeNoWhether to filter subcategory nodes; only takes effect when nodeLabel or nodeIdPath has a value
includeBrandsNoContains brand; maxLength 10240
maxVariationsNoHighest number of variants
minVariationsNoMinimum number of variants
showVariationNoWhether to query variants: `Y` or `N`N
excludeSellersNoExclude sellers; maxLength 10240
includeSellersNoIncludes seller; maxLength 10240
badgeBestSellerNoBest Seller Logo: `Y`, `N` or leave blank
badgeNewReleaseNoNew Release ID: `Y`, `N` or leave blank
excludeKeywordsNoExclude keywords; maxLength 10240
maxBsrGrowthRateNoBSR maximum growth rate, unit %
minBsrGrowthRateNoBSR minimum growth rate, unit %
dataSnapshotMonthNoProduct data snapshot year and month in `yyyyMM` format, or `nearly` representing the last 30 days of real-time data; maxLength 1000nearly
maxBsrGrowthCountNoBSR highest growth number
maxSubNodeBsrRankNoSubcategory BSR maximum ranking; requires `filterSubNode=true`
minBsrGrowthCountNoBSR minimum growth number
minSubNodeBsrRankNoSubcategory BSR lowest ranking; requires `filterSubNode=true`
badgeAmazonsChoiceNoAmazon's Choice logo: `Y`, `N` or leave blank
maxUnitsGrowthRateNoMaximum monthly sales growth rate, unit %
minUnitsGrowthRateNoMinimum monthly sales growth rate, unit %
hideUnlistedProductNoWhether to hide removed products
maxRatingsGrowthCountNoHighest number of new ratings per month (>= 0)
minRatingsGrowthCountNoMinimum number of new ratings per month (>= 0)
listedWithinLastMonthsNoShelf time range (months), only `1`, `3`, `6`, `12`, `24` allowed
maxListingQualityScoreNoHighest Listing page quality score (>= 0)
minListingQualityScoreNoMinimum Listing page quality score (>= 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.7/5.0
Behavior1/5

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

Annotations only state readOnlyHint=false and openWorldHint=true, and the description adds nothing beyond that: no mention of pagination limits, the effect of dataSnapshotMonth vs 'nearly', sorting defaults, or result caps. For a 65-parameter query tool the description carries no behavioral context whatsoever.

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?

It is a single sentence that duplicates the title verbatim, so there is no wasted length but also no information. Being short here reflects under-specification rather than disciplined concision.

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

Completeness1/5

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

With 65 optional parameters, nested sorting, snapshot-month semantics, and no output schema, the description should explain what a call returns and how to scope it. It says nothing, leaving the agent entirely dependent on field names.

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% and every parameter, including the nested order object, has an inline description with ranges and allowed values. The description itself adds no parameter meaning, so this rests at the baseline for a fully documented schema.

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 merely restates the tool name and title ('product Search API') with no scope, data source, or return content. With dozens of sibling product-search tools (nexscope_amazon_market_product_search, nexscope_amazon_broad_product_search, nexscope_data_ss_market_research, etc.), nothing here tells an agent how this one differs.

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 when-to-use, when-not-to-use, or alternative-referencing guidance at all. An agent cannot infer from 'product Search API' whether this is for keyword research, sales estimation, competitor discovery, or something else.

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