Skip to main content
Glama

openapi_v2_products_search

Search Amazon products

  1. Function

Discover candidate Amazon products by keyword, category and business metrics, returning a paginated list of the shared Product model (max 100 per page). Reads the catalog snapshot: omit dateRange or pass 'Nd' for the latest daily snapshot, or 'YYYY-MM' for that month's month-end snapshot (earliest 2026-02). Filters include price, monthly sales and revenue floors, growth rates, BSR and its 7-day change, rating, seller count, brand and seller lists, badges, fulfillment, package weight in ounces, package size tier, Buy Box seller country, gross margin rate and category scope. Setting any range or list filter excludes products whose value is unknown, so a narrower result set is a coverage effect, not a market finding. categoryScope=includeChildren (default) matches the given category levels and every subcategory; exactOnly requires the product's path to end at the last given level. monthlySalesFloor is the page's 'N+ bought in past month' figure carried forward by the catalog snapshot, a lower bound rather than an estimate. Billing: 1 credit per request.

  1. Use cases

Use search to find products you do not know yet — niche discovery, competitor screening, filtering by margin or growth. Use /products/detail to read ASINs or a parent's variants you already know; it takes no filters. Use /products/competitors for competitor lookup around one ASIN, and /markets/search for category-level demand and competition.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

Example Response:

{
  "success": true,
  "meta": {
    "requestId": "Requestid",
    "timestamp": "Timestamp"
  }
}

Output Schema:

{
  "properties": {
    "success": {
      "type": "boolean",
      "title": "Success",
      "description": "Whether the request was successful",
      "default": true
    },
    "data": {
      "title": "Data",
      "description": "Response data payload"
    },
    "error": {
      "description": "Error details if request failed"
    },
    "meta": {
      "description": "Metadata for API responses.\n\nCredit fields follow the ADR-0003 parallel-fields strategy (Option 3):\n- `credits_remaining` / `credits_consumed` (int): legacy fields, rounded\n  to whole credits, kept for zero-breaking-change to existing SDK clients.\n- `credits_remaining_exact` / `credits_consumed_exact` (float): new\n  precision-aware fields for clients that opt in to decimal credits.\n\nSee ADR-0003 decision 5 and the \u00a78 deprecation timeline.\n\nTODO(2026-11, ADR-0003 \u00a78 +6mo): mark `credits_remaining` /\n`credits_consumed` as `deprecated=True` in their Field() definitions\nand announce in customer changelog.\nTODO(2027-05, ADR-0003 \u00a78 +12mo): remove the legacy int fields via a\nmajor-version bump of the OpenAPI surface.",
      "properties": {
        "requestId": {
          "type": "string",
          "title": "Requestid",
          "description": "Unique request identifier"
        },
        "timestamp": {
          "type": "string",
          "title": "Timestamp",
          "description": "Response timestamp in ISO 8601 format"
        },
        "total": {
          "title": "Total",
          "description": "Total number of records"
        },
        "page": {
          "title": "Page",
          "description": "Current page number"
        },
        "pageSize": {
          "title": "Pagesize",
          "description": "Number of records per page"
        },
        "totalPages": {
          "title": "Totalpages",
          "description": "Total number of pages"
        },
        "creditsRemaining": {
          "title": "Creditsremaining",
          "description": "Remaining API credits (rounded to whole credits; see creditsRemainingExact for precise value)"
        },
        "creditsConsumed": {
          "title": "Creditsconsumed",
          "description": "Credits consumed by this request (rounded; see creditsConsumedExact for precise value)"
        },
        "creditsRemainingExact": {
          "title": "Creditsremainingexact",
          "description": "Remaining API credits, precise to 1 decimal place"
        },
        "creditsConsumedExact": {
          "title": "Creditsconsumedexact",
          "description": "Credits consumed by this request, precise to 1 decimal place"
        },
        "tokensUsage": {
          "description": "Provider token-usage block \u2014 populated on terminal video polls only, null on every non-video endpoint. See TokensUsage for its fields."
        }
      },
      "type": "object",
      "required": [
        "requestId",
        "timestamp"
      ],
      "title": "ResponseMeta"
    }
  },
  "type": "object",
  "required": [
    "meta"
  ],
  "title": "OpenApiResponse[list[Product]]",
  "examples": []
}

422: Validation Error Content-Type: application/json

Example Response:

{
  "detail": [
    {
      "loc": [],
      "msg": "Message",
      "type": "Error Type",
      "ctx": {}
    }
  ]
}

Output Schema:

{
  "properties": {
    "detail": {
      "items": {
        "properties": {
          "loc": {
            "items": {},
            "type": "array",
            "title": "Location"
          },
          "msg": {
            "type": "string",
            "title": "Message"
          },
          "type": {
            "type": "string",
            "title": "Error Type"
          },
          "input": {
            "title": "Input"
          },
          "ctx": {
            "type": "object",
            "title": "Context"
          }
        },
        "type": "object",
        "required": [
          "loc",
          "msg",
          "type"
        ],
        "title": "ValidationError"
      },
      "type": "array",
      "title": "Detail"
    }
  },
  "type": "object",
  "title": "HTTPValidationError"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
badgesNoInclude products with these badges. Example: ['bestSeller', 'amazonChoice', 'newRelease', 'aPlus', 'video'].
bsrMaxNoMaximum Best Sellers Rank. Example: 100000.
bsrMinNoMinimum Best Sellers Rank (lower = better). Example: 1.
lqsMaxNoMaximum Listing Quality Score. No data in the source currently.
lqsMinNoMinimum Listing Quality Score. No data in the source currently.
sortByNoSort fieldmonthlySalesFloor
keywordNoSearch keyword
pageSizeNoPage size
priceMaxNoMaximum product price. Example: 99.99.
priceMinNoMinimum product price. Example: 9.99.
dateRangeNoAggregation window for metrics like monthly sales, revenue, and rating count. Null or '30d' — last 30 days (default). 'YYYY-MM' — that calendar month, e.g. '2026-04'. Available months: '2026-02' up to the most recent completed month.
fbaFeeMaxNoMaximum FBA fee. Example: 15.00.
fbaFeeMinNoMinimum FBA fee. Example: 3.00.
ratingMaxNoMaximum star rating (0.0-5.0). Example: 5.0.
ratingMinNoMinimum star rating (0.0-5.0). Example: 4.0.
sortOrderNoSort direction: asc or descdesc
subBsrMaxNoMaximum sub-category BSR. Example: 50000.
subBsrMinNoMinimum sub-category BSR. Example: 1.
listingAgeNoMax product age: '30d', '90d', '180d', '1y', '2y'. Null = no limit.
qaCountMaxNoMaximum Q&A count. Example: 100.
qaCountMinNoMinimum Q&A count. Example: 5.
marketplaceNoAmazon marketplace code. Only 'US' is currently supported.US
bsrGrowthMaxNoMaximum 7-day main-category BSR change (see bsrGrowthMin).
bsrGrowthMinNoMinimum 7-day main-category BSR change = rank 7 days ago − rank today; positive means the rank improved. bsrGrowthMin=1000 keeps products that moved up at least 1000 places. Negative allowed. About 70.7% of products have a value. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding.
categoryPathNoCategory hierarchy from root to current level (e.g., ['Electronics', 'Computers', 'Laptops'])
fulfillmentsNoFulfillment filter. Example: ['FBA', 'FBM'].
categoryScopeNoincludeChildren (default): categoryPath matches the given levels, so every subcategory is included. exactOnly: the product's category path must end at the last given level. Ignored without categoryPath; exactOnly without categoryPath is rejected with category_scope_requires_category_path.includeChildren
excludeBadgesNoExclude products with these badges. Supported: ['aPlus', 'video'].
excludeBrandsNoBrand names to exclude. Example: ['Generic'].
includeBrandsNoBrand names to include. Example: ['Apple', 'Samsung'].
excludeSellersNoSeller names to exclude.
includeSellersNoSeller names to include. Example: ['Apple Store'].
ratingCountMaxNoMaximum total rating count. Example: 10000.
ratingCountMinNoMinimum total rating count. Example: 50.
sellerCountMaxNoMaximum number of sellers. Example: 20.
sellerCountMinNoMinimum number of sellers. Example: 1.
excludeKeywordsNoKeywords to exclude from results. Example: ['refurbished', 'used'].
monthlySalesMaxNoMaximum monthly sales floor. Units sold. Example: 5000.
monthlySalesMinNoMinimum monthly sales floor. Units sold. Example: 100.
subBsrGrowthMaxNoMaximum 7-day sub-category BSR change (see subBsrGrowthMin).
subBsrGrowthMinNoMinimum 7-day sub-category BSR change (rank 7 days ago − rank today; positive = improved). Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding.
variantCountMaxNoMaximum number of product variants. Example: 50.
variantCountMinNoMinimum number of product variants. Example: 2.
bsrGrowthRateMaxNoMaximum BSR growth rate as decimal.
bsrGrowthRateMinNoMinimum BSR growth rate as decimal. Example: -0.2 = 20% improvement.
keywordMatchTypeNoKeyword match type: 'fuzzy', 'phrase', or 'exact'. Null = fuzzy.
onlyCategoryRankNoIf true, only return products ranked in their category BSR.
packageSizeTypesNoPackage size tiers (US 2024-25 FBA tiers): smallStandard, largeStandard, largeBulky, extraLarge. Mostly inferred from weight alone (dimensions cover ~2% of products), so a light but long item can be classed smallStandard. About 31.4% of products have a tier. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding.
packageWeightMaxNoMaximum package weight in ounces (see packageWeightMin).
packageWeightMinNoMinimum package weight in ounces (page 'Item Weight' converted; same unit as /markets/search). About 31.4% of products have a value. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding. Populated from the 2026-09-16 snapshot onward; month-end snapshots (dateRange='YYYY-MM') before that have no value.
monthlyRevenueMaxNoMaximum monthly revenue floor. Example: 50000.00.
monthlyRevenueMinNoMinimum monthly revenue floor. Example: 1000.00.
grossMarginRateMaxNoMaximum gross margin rate, 0-1 (see grossMarginRateMin).
grossMarginRateMinNoMinimum gross margin rate, 0-1: (price − FBA fee) ÷ price; excludes referral fee and cost of goods. Products with unknown FBA fee are excluded. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding. Populated from the 2026-09-16 snapshot onward; month-end snapshots (dateRange='YYYY-MM') before that have no value.
ratingFilterTargetNoChoose whether rating-related filters apply to the current product or the most-rated variant.
salesGrowthRateMaxNoMaximum sales growth rate as decimal. Example: 0.5 = 50% growth.
salesGrowthRateMinNoMinimum sales growth rate as decimal. Example: 0.1 = 10% growth.
ratingToSalesRateMaxNoMaximum rating-to-sales rate as decimal. Example: 0.5.
ratingToSalesRateMinNoMinimum rating-to-sales rate as decimal. Example: 0.05.
monthlyRatingCountMaxNoMaximum monthly new rating count. Example: 500.
monthlyRatingCountMinNoMinimum monthly new rating count. Example: 10.
parentMonthlySalesMaxNoMaximum parent ASIN monthly sales floor. Units sold.
parentMonthlySalesMinNoMinimum parent ASIN monthly sales floor. Units sold.
buyBoxSellerCountryCodesNoBuy Box seller country codes, two uppercase letters each, e.g. ['CN', 'US']. About 88.7% of products have a value. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding.
monthlyRevenueGrowthRateMaxNoMaximum monthly revenue growth rate as decimal (see monthlyRevenueGrowthRateMin).
monthlyRevenueGrowthRateMinNoMinimum monthly revenue growth rate as decimal: today's monthlyRevenueFloor vs the same-basis value 30 days earlier, minus 1. About 3.7% of products have a value. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding. Populated from the 2026-09-16 snapshot onward; month-end snapshots (dateRange='YYYY-MM') before that have no value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedInput schema / properties / bsrGrowthMax
      Added value: +{
      +  "description": "Maximum 7-day main-category BSR change (see bsrGrowthMin).",
      +  "title": "bsrGrowthMax",
      +  "type": "integer"
      +}
    • addedInput schema / properties / bsrGrowthMin
      Added value: +{
      +  "description": "Minimum 7-day main-category BSR change = rank 7 days ago − rank today; positive means the rank improved. bsrGrowthMin=1000 keeps products that moved up at least 1000 places. Negative allowed. About 70.7% of products have a value. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding.",
      +  "title": "bsrGrowthMin",
      +  "type": "integer"
      +}
    • addedInput schema / properties / buyBoxSellerCountryCodes
      Added value: +{
      +  "description": "Buy Box seller country codes, two uppercase letters each, e.g. ['CN', 'US']. About 88.7% of products have a value. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "minItems": 1,
      +  "title": "buyBoxSellerCountryCodes",
      +  "type": "array"
      +}
    • addedInput schema / properties / categoryScope
      Added value: +{
      +  "default": "includeChildren",
      +  "description": "includeChildren (default): categoryPath matches the given levels, so every subcategory is included. exactOnly: the product's category path must end at the last given level. Ignored without categoryPath; exactOnly without categoryPath is rejected with category_scope_requires_category_path.",
      +  "enum": [
      +    "includeChildren",
      +    "exactOnly"
      +  ],
      +  "title": "categoryScope",
      +  "type": "string"
      +}
    • addedInput schema / properties / grossMarginRateMax
      Added value: +{
      +  "description": "Maximum gross margin rate, 0-1 (see grossMarginRateMin).",
      +  "maximum": 1,
      +  "minimum": 0,
      +  "title": "grossMarginRateMax",
      +  "type": "number"
      +}
    • addedInput schema / properties / grossMarginRateMin
      Added value: +{
      +  "description": "Minimum gross margin rate, 0-1: (price − FBA fee) ÷ price; excludes referral fee and cost of goods. Products with unknown FBA fee are excluded. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding. Populated from the 2026-09-16 snapshot onward; month-end snapshots (dateRange='YYYY-MM') before that have no value.",
      +  "maximum": 1,
      +  "minimum": 0,
      +  "title": "grossMarginRateMin",
      +  "type": "number"
      +}
    • changedInput schema / properties / lqsMax / description
      Previous value: -"Maximum Listing Quality Score"New value: +"Maximum Listing Quality Score. No data in the source currently."
    • changedInput schema / properties / lqsMin / description
      Previous value: -"Minimum Listing Quality Score"New value: +"Minimum Listing Quality Score. No data in the source currently."
    • addedInput schema / properties / monthlyRevenueGrowthRateMax
      Added value: +{
      +  "description": "Maximum monthly revenue growth rate as decimal (see monthlyRevenueGrowthRateMin).",
      +  "title": "monthlyRevenueGrowthRateMax",
      +  "type": "number"
      +}
    • addedInput schema / properties / monthlyRevenueGrowthRateMin
      Added value: +{
      +  "description": "Minimum monthly revenue growth rate as decimal: today's monthlyRevenueFloor vs the same-basis value 30 days earlier, minus 1. About 3.7% of products have a value. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding. Populated from the 2026-09-16 snapshot onward; month-end snapshots (dateRange='YYYY-MM') before that have no value.",
      +  "title": "monthlyRevenueGrowthRateMin",
      +  "type": "number"
      +}
    • addedInput schema / properties / packageSizeTypes
      Added value: +{
      +  "description": "Package size tiers (US 2024-25 FBA tiers): smallStandard, largeStandard, largeBulky, extraLarge. Mostly inferred from weight alone (dimensions cover ~2% of products), so a light but long item can be classed smallStandard. About 31.4% of products have a tier. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding.",
      +  "items": {
      +    "enum": [
      +      "smallStandard",
      +      "largeStandard",
      +      "largeBulky",
      +      "extraLarge"
      +    ],
      +    "type": "string"
      +  },
      +  "minItems": 1,
      +  "title": "packageSizeTypes",
      +  "type": "array"
      +}
    • addedInput schema / properties / packageWeightMax
      Added value: +{
      +  "description": "Maximum package weight in ounces (see packageWeightMin).",
      +  "minimum": 0,
      +  "title": "packageWeightMax",
      +  "type": "number"
      +}
    • addedInput schema / properties / packageWeightMin
      Added value: +{
      +  "description": "Minimum package weight in ounces (page 'Item Weight' converted; same unit as /markets/search). About 31.4% of products have a value. Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding. Populated from the 2026-09-16 snapshot onward; month-end snapshots (dateRange='YYYY-MM') before that have no value.",
      +  "minimum": 0,
      +  "title": "packageWeightMin",
      +  "type": "number"
      +}
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
      -  "monthlySalesFloor",
      -  "monthlyRevenueFloor",
      -  "salesGrowthRate",
      -  "bsrGrowthRate",
      -  "bsr",
      -  "price",
      -  "rating",
      -  "ratingCount",
      -  "listingDate"
      -]New value: +[
      +  "monthlySalesFloor",
      +  "monthlyRevenueFloor",
      +  "salesGrowthRate",
      +  "bsrGrowthRate",
      +  "bsr",
      +  "price",
      +  "rating",
      +  "ratingCount",
      +  "listingDate",
      +  "grossMarginRate",
      +  "monthlyRevenueGrowthRate",
      +  "bsrGrowth"
      +]
    • addedInput schema / properties / subBsrGrowthMax
      Added value: +{
      +  "description": "Maximum 7-day sub-category BSR change (see subBsrGrowthMin).",
      +  "title": "subBsrGrowthMax",
      +  "type": "integer"
      +}
    • addedInput schema / properties / subBsrGrowthMin
      Added value: +{
      +  "description": "Minimum 7-day sub-category BSR change (rank 7 days ago − rank today; positive = improved). Setting this excludes products whose value is unknown — a narrower candidate set, not a market finding.",
      +  "title": "subBsrGrowthMin",
      +  "type": "integer"
      +}
  2. Changed5 schema fields changed
    • addedInput schema / properties / marketplace / const
      Added value: +"US"
    • changedInput schema / properties / marketplace / description
      Previous value: -"Amazon marketplace code"New value: +"Amazon marketplace code. Only 'US' is currently supported."
    • removedInput schema / properties / marketplace / enum
      Removed value: -[
      -  "US",
      -  "UK"
      -]
    • removedInput schema / properties / marketplace / x-unsupported-values
      Removed value: -[
      -  "UK"
      -]
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
      -  "monthlySalesFloor",
      -  "monthlyRevenueFloor",
      -  "bsr",
      -  "price",
      -  "rating",
      -  "ratingCount",
      -  "listingDate"
      -]New value: +[
      +  "monthlySalesFloor",
      +  "monthlyRevenueFloor",
      +  "salesGrowthRate",
      +  "bsrGrowthRate",
      +  "bsr",
      +  "price",
      +  "rating",
      +  "ratingCount",
      +  "listingDate"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / dateRange / description
      Previous value: -"Aggregation window for metrics like monthly sales, revenue, and rating count. Null or '30d' — last 30 days (default). 'YYYY-MM' — that calendar month, e.g. '2026-04'. Available months: '2026-02' up to the most recent completed month.\n\n聚合窗口(月销量、月营收、月评论数等指标)。null 或 '30d' — 最近 30 天(默认)。'YYYY-MM' — 该自然月,如 '2026-04'。可选月份:'2026-02' 至最近一个已完结的月份。"New value: +"Aggregation window for metrics like monthly sales, revenue, and rating count. Null or '30d' — last 30 days (default). 'YYYY-MM' — that calendar month, e.g. '2026-04'. Available months: '2026-02' up to the most recent completed month."
  4. Changed1 schema field changed
    • changedInput schema / properties / dateRange / description
      Previous value: -"Time range filter. Relative ('30d') or month ('2026-02'). Null = latest."New value: +"Aggregation window for metrics like monthly sales, revenue, and rating count. Null or '30d' — last 30 days (default). 'YYYY-MM' — that calendar month, e.g. '2026-04'. Available months: '2026-02' up to the most recent completed month.\n\n聚合窗口(月销量、月营收、月评论数等指标)。null 或 '30d' — 最近 30 天(默认)。'YYYY-MM' — 该自然月,如 '2026-04'。可选月份:'2026-02' 至最近一个已完结的月份。"
  5. Changed1 schema field changed
    • changedInput schema / properties / pageSize / description
      Previous value: -"Page size (max 100)"New value: +"Page size"
  6. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations present, the description carries the full behavioral burden and does so thoroughly. It discloses that the tool reads a catalog snapshot, charges 1 credit per request, explains that range/list filters exclude unknown values as a coverage effect rather than a market finding, and clarifies that monthlySalesFloor is a lower bound. These are non-obvious behavioral traits an agent would otherwise not know.

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

Conciseness5/5

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

The description is long but appropriately structured for a 67-parameter tool: a compact function summary, then use-case routing. It is front-loaded with the most decision-relevant facts and has no filler. Each section earns its place by clarifying scope, semantics, billing, or alternatives.

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

Completeness5/5

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

Given the tool's complexity and the absence of annotations, the description is complete for invocation purposes. It covers what the tool returns, pagination limits, snapshot semantics, billing, filter semantics, caveats, and when to choose sibling tools. The opaque Product model in the response schema is a minor gap, but the agent has enough to select and call the tool correctly.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds meaning beyond the schema by grouping the 67 filters into semantic categories and explaining cross-cutting behaviors: coverage effects, snapshot date semantics, category scope behavior, package-size inference caveats, and the gross margin formula. It also clarifies how monthlySalesFloor relates to the 'N+ bought in past month' figure, which is not evident from parameter names alone.

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

Purpose5/5

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

The description opens with a specific verb and resource ('Search Amazon products') and immediately states the function: discover candidate products by keyword, category, and business metrics, returning a paginated list. It also names sibling tools like /products/detail and /products/competitors, which distinguishes this search tool from alternative product endpoints.

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

Usage Guidelines5/5

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

Section 2 explicitly states when to use search: to find products you do not know yet, such as niche discovery and competitor screening. It then names the alternatives and their conditions: use products/detail for known ASINs, products/competitors for lookup around one ASIN, and markets/search for category-level demand. This is explicit routing guidance.

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