Nexscope Ecommerce Data MCP

Amazon History KP: product Search API

nexscope_data_kp_product_search

Amazon History KP: product Search API.

Input Schema

Name	Required	Description
`page`	No	Page number, starting from 1.
`size`	No	Size, OR match.
`sort`	No	Maximum of 3 collations; each contains `{"fieldName":"...","sortDirection":"asc\\|desc"}`. Sortable fields: `availableDate`, `currentSales`, `monthlySold`, `currentRating`, `currentCountReviews`, `currentBuyBoxShipping`, `currentNew`.
`brand`	No	Brand, OR match.
`color`	No	Color, OR match.
`domain`	Yes	Amazon domain name ID: `1`=USA, `2`=UK, `3`=Germany, `4`=France, `5`=Japan, `6`=Canada, `8`=Italy, `9`=Spain, `10`=India, `11`=Mexico.
`rating`	No	Whether to obtain rating information: `1`=obtain, `0`=not obtain.
`history`	No	Whether the return value contains historical data/historical sales volume: `1`=obtain, `0`=not obtain.
`keyword`	No	Title keyword; case-insensitive, spaces represent word segmentation AND, when the keyword itself contains spaces, it should be wrapped in double quotes, and the prefix `-` is supported for exclusion; `&` will be replaced by spaces, with a maximum of 50 keywords and a maximum of 1000 characters.
`perPage`	No	The maximum number of results returned per page, minimum 50, maximum 100.
`isHazMat`	No	Whether it is dangerous goods.
`srAvgMonth`	No	Historical sales ranking month, format `YYYYMM`, within the last 36 months.
`buyBoxIsFBA`	No	Whether the Buy Box is FBA.
`productType`	No	Product Types: `0`=Standard Product, `1`=Downloadable Product, `2`=Ebook, `5`=Variant Parent ASIN.
`rootCategory`	No	Root category ID, up to 50.
`buyBoxIsAmazon`	No	Whether the Buy Box seller is Amazon.
`singleVariation`	No	Only one variant is returned; when set to `true`, only one variant is returned for multi-variant products.
`categoriesExclude`	No	Subcategory IDs to exclude, up to 50.
`categoriesInclude`	No	Subcategory IDs to include, up to 50; only include products listed directly in these subcategories.
`rootCategoryNames`	No	Root category name, up to 50; used when `rootCategory` is empty, the system automatically searches for the corresponding category ID.
`categoriesExcludeNames`	No	Names of subcategories to be excluded, up to 50; used when `categoriesExclude` is empty, supporting full category paths.
`categoriesIncludeNames`	No	Subcategory names to include, up to 50; used when `categoriesInclude` is empty, supports full category paths separated by `:` or `›`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

D1.7/5.0

Behavior1/5

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

The annotations only declare readOnlyHint=false and openWorldHint=true, so the description carries most of the burden and delivers nothing: no indication of what the call returns, whether pagination or quotas apply, or what the special history/rating flags change. A 22-parameter search endpoint described in nine words leaves behavior entirely opaque.

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 fragment with zero waste, but brevity here reflects under-specification rather than efficient communication. Nothing is front-loaded because nothing is stated beyond the title.

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?

For a 22-parameter, high-complexity search tool with no output schema and only minimal annotations, the description supplies none of the context an agent needs. It neither explains the KP/History data source nor what results look like.

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% across all 22 parameters, including enum mappings (domain, productType), sortable fields, and limits, so the schema does the explanatory work. The description adds no parameter meaning beyond the schema, which is the expected baseline-3 outcome at full coverage.

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 almost verbatim: "Amazon History KP: product Search API." It names a resource (Amazon products) and implies search, but gives no scope, no data source detail, and nothing that separates it from the many sibling search tools such as nexscope_data_kp_product_request, nexscope_data_kp_product_series, or nexscope_amazon_product_search.

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 guidance, no exclusions, and no mention of alternatives. With dozens of sibling product-search tools available, an agent has no basis in this description for choosing this one over nexscope_amazon_product_search or nexscope_data_kp_product_request.

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

All Nexscope Ecommerce Data MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?