Tool Reference
Amazon Catalog MCP Tool Reference
Amazon catalog MCP reference for product details, listing quality, A+ Content, reviews, variations, listing creation, FBA conversion, price updates, and quantity updates.
Use this Amazon catalog MCP reference for product details, listing quality, A+ Content, variations, reviews, listing creation, existing-SKU FBA conversion, price updates, and quantity updates.
Related paths
Hosted Amazon Seller Central MCP overview for Claude, ChatGPT, and custom agents.
Amazon Ads MCP serverPrimary Ads MCP page for campaigns, search terms, budget pacing, TACOS, retained history, and guarded Ads writes.
Amazon MCP server for ClaudeClaude-specific page for Amazon Seller Central, Amazon Ads, inventory, orders, catalog, finance, and fulfillment data.
Amazon seller data for AI agentsHow ads, inventory, orders, catalog, finance, and fulfillment data are structured for agents.
Claude connection walkthroughStep-by-step path from Seller Central OAuth to a Claude connector or MCP config.
ChatGPT Seller Central setupChatGPT-specific setup and examples for Amazon seller data through MCP.
Tools (16)
read
write
live api
hybrid
read
get_product_details
readGet product info for a specific ASIN from the catalog. Title, brand, product type, images, dimensions, status, and BSR (Best Sellers Rank) at two grains: the specific subcategory rank and the top-level main category rank.
When to use
Look up detailed product information for a specific ASIN, including title, dimensions, images, and current BSR.
Parameters2
| Name | Type | Description |
|---|---|---|
asin* | string | ASIN to look up. |
include_raw_rows | boolean (true) | Set false to return a compact row preview. Defaults to true; large result sets are capped automatically to keep the response manageable. |
* required
Tips
- Check item_status to verify the product is in an active state.
- sales_rank/sales_rank_category is the most specific subcategory rank; main_category_rank/main_category is the headline "#N in <Department>" rank shown on the product page.
- BSR gives a relative indicator of sales volume within its category. Lower is better.
- Image URLs and bullet_points are useful for listing audit workflows.
Related tools
get_sales_ranks
readGet Best Sellers Rank (BSR) across your catalog. Returns the subcategory rank (sales_rank, sales_rank_category) and the top-level main category rank (main_category_rank, main_category), plus title and brand, for all ASINs with BSR data.
When to use
Monitor BSR across your entire catalog to identify top sellers and products losing rank.
Parameters7
| Name | Type | Description |
|---|---|---|
asin | string | Filter by ASIN. |
max_rank | number | Only show ASINs whose subcategory sales_rank is less than or equal to this value. |
sort_by | enum (sales_rank) | Column to sort by: sales_rank, main_category_rank, asin, title. |
sort_order | enum (asc) | Sort direction: asc or desc. Default asc shows best rank first. |
limit | number (20) | Max rows to return (1-1000). |
offset | number (0) | Pagination offset. Continue with pagination.next_offset from the previous response. |
include_raw_rows | boolean (true) | Set false to return a compact row preview. Defaults to true; large result sets are capped automatically to keep the response manageable. |
Tips
- sales_rank is the most specific subcategory rank; main_category_rank is the broad department rank ("#N in <Department>"). The two can differ by orders of magnitude.
- Use max_rank=10000 to focus on products in the top 10,000 of their subcategory.
- Lower BSR means higher sales velocity. Track BSR trends over time by running this daily.
- Compare BSR against actual sales data from get_sales_velocity to validate.
get_aplus_status
readCheck A+ Content status for your listings. Shows content documents with their approval status, associated ASINs, and last update time. Requires Brand Registry.
When to use
Audit which listings have A+ Content, check approval statuses, and identify products that are missing enhanced content.
Tips
- A+ Content typically improves conversion rates by 3-10%, so identify ASINs without it.
- Check the status field for content that may be pending review or rejected.
- Cross-reference the ASINs list against your active listings to find gaps.
Watch out
- Requires Brand Registry enrollment. Returns empty results if Brand Registry is not active.
get_variations
readGet parent/child variation relationships for an ASIN. Shows the variation family tree including variation theme (size, color, etc.) and all child ASINs.
When to use
Understand the variation family structure for a product, find all child ASINs under a parent, or determine if an ASIN is a parent or child.
Parameters1
| Name | Type | Description |
|---|---|---|
asin* | string | Parent or child ASIN to look up variation relationships for. |
* required
Tips
- Pass either a parent or child ASIN and the tool will show the full family tree.
- The variation theme (size, color, etc.) tells you which attribute differentiates the children.
- Use this to identify all child ASINs when you need to check inventory or pricing across the family.
get_listing_quality
readGet weekly Listings Items API quality snapshots. view=summary returns listing completeness and issue counts; view=issues returns Amazon issue codes, affected attributes, and raw issue details.
When to use
Use this to inspect listing completeness, Amazon listing issue signals, missing content, offer/fulfillment availability counts, and source-provided issue details.
Parameters15
| Name | Type | Description |
|---|---|---|
asin | string | Filter by ASIN. |
sku | string | Filter by SKU. |
sort_order | enum (desc) | Sort direction: asc or desc. |
limit | number (20) | Max rows to query (1-1000). Use a higher limit when the user asks for all matching rows; large responses are capped automatically. |
view | enum (summary) | summary returns listing completeness and issue counts; issues returns Amazon issue details. |
snapshot_date | string | Optional snapshot date (YYYY-MM-DD). Defaults to latest listing quality snapshot. |
include_synthetic_skus | boolean (false) | Include reimbursement placeholder SKUs such as FBA...missing1. |
quality_status | enum | summary view only. Filter by healthy, incomplete, warning, error, or not_found. |
has_issues | boolean | summary view only. True returns listings with issue_count > 0; false returns zero-issue rows. |
severity | enum | issues view only. Filter by ERROR, WARNING, or INFO. |
issue_code | string | issues view only. Filter listings containing a specific Amazon issue code. |
attribute_name | string | issues view only. Filter listings containing an issue for this attribute name. |
sort_by | enum (issue_count) | Sort column. Allowed columns depend on view. |
offset | number (0) | Pagination offset. Continue with pagination.next_offset from the previous response. |
include_raw_rows | boolean (true) | Set false to return a compact row preview. Defaults to true; large result sets are capped automatically to keep the response manageable. |
Tips
- Use view="summary" to scan listing completeness and issue counts.
- Use view="issues" to inspect Amazon issue codes, affected attributes, and raw issue JSON.
- Filter by asin or sku when reviewing one listing before an update_listing preview.
Watch out
- Snapshots refresh weekly. For a live 'is this ASIN buyable right now' check, fan out across get_buybox_status, get_listing_restrictions, and get_fba_eligibility (all live SP-API), and cross-reference get_suppressed_listings.
get_catalog_cleanup
readReturn listing quality signals from snapshots: Amazon errors, warnings, missing core content, offer and fulfillment gaps, and thin listing content.
When to use
Inspect listing quality states across Amazon issues, missing content, offer availability, and fulfillment availability.
Parameters6
| Name | Type | Description |
|---|---|---|
asin | string | Filter by ASIN. |
sku | string | Filter by seller SKU. |
snapshot_date | string | Snapshot date (YYYY-MM-DD). Defaults to latest listing quality snapshot. |
cleanup_focus | enum (all) | Focus category: all, amazon_error, amazon_warning, missing_core_content, offer_or_fulfillment_gap, or content_depth_gap. |
include_healthy | boolean (false) | Include healthy listings after cleanup items. |
limit | number (20) | Max cleanup rows to return (1-100). |
Tips
- Run with cleanup_focus=amazon_error to return rows with Amazon error-level listing issues.
- Use cleanup_focus=missing_core_content to find listings missing title, brand, or main image.
- Use cleanup_reasons and issue_attribute_names to group rows by captured listing quality signal.
Watch out
- The tool reads weekly listing quality snapshots; it does not perform live Seller Central validation. Use update_listing in preview mode before submitting changes.
get_listing_content_changes
readDetect changes to listing content by comparing the two most recent snapshots per item. Diffs title, brand, description, main image, bullet points, and the full image set from the catalog snapshot, plus backend search terms (generic_keyword) from the weekly Listings Items snapshot. Returns one row per changed field with its previous and current value.
When to use
Use this to see what listing content actually changed between snapshots: title, brand, or description edits, main-image swaps, bullet rewrites, gallery-image changes, and backend keyword changes.
Parameters4
| Name | Type | Description |
|---|---|---|
asin | string | Filter to a single ASIN (exact match). |
lookback_days | number (30) | How many days of snapshots to consider when finding the two most recent per item. Covers roughly four weekly Listings Items snapshots for keyword changes. |
limit | number (100) | Max changed-field rows to return (1-500). |
offset | number (0) | Pagination offset. Continue with pagination.next_offset from the previous response. |
Tips
- Each row is one changed field with previous_value and current_value, so you can see exactly what changed. The source field tags whether it came from the catalog diff or the keyword diff.
- Array fields (bullet_points, image_urls) are compared as JSON, so a reordering counts as a change. The image set covers the full gallery, not just the main image.
- Backend search-term changes diff at weekly cadence and need two weekly Listings Items snapshots before they appear.
Watch out
- Amazon exposes no native listing edit-history API; this is computed from agentcentral's own snapshots, so it only sees changes from one captured snapshot to the next and a recent edit appears once the following snapshot lands.
- Video and A+ module-level content are not diffed: Amazon has no supported read feed for listing video, and A+ change status plus last-update time is on get_aplus_status.
get_product_type_definition
readReturn the marketplace's canonical Amazon Product Type Definition (PTD) for one product type. The default summary is a bounded overview: up to 500 attributes and 50 enum values per attribute, marked complete=false with counts and truncation details. Pass attributes in summary view to get every value plus the selected properties' raw schemas, relevant conditional constraints, and transitive local references. Schema view returns the full Amazon JSON schema when it fits the response ceiling. Live Amazon data, cached five minutes.
When to use
Use this before update_listing or create_listing when an attribute accepts a limited set of values, for example diet_type or allergen_information on a Grocery product type, so the agent can set the accepted key instead of guessing.
Parameters8
| Name | Type | Description |
|---|---|---|
product_type* | string | Amazon product type, e.g. SAUCE or HOME. agentcentral resolves the canonical type for the marketplace. |
view | enum (summary) | summary returns a bounded overview, or complete targeted details when attributes are supplied; schema returns the full Amazon JSON schema. |
requirements | enum (LISTING) | Requirements level: LISTING, LISTING_PRODUCT_ONLY, or LISTING_OFFER_ONLY. |
requirements_enforced | enum (ENFORCED) | ENFORCED or NOT_ENFORCED. |
parentage_level | enum (NONE) | CHILD, PARENT, or NONE. |
locale | string | Optional locale, e.g. en_US. |
version | string | Optional specific product type version. |
attributes | string[] | Optional selection of up to 50 attributes in summary view. Selected attributes return every enum value plus raw property schemas, relevant conditional constraints, and transitive local references. |
* required
Tips
- The Listings Items API takes the enum key, not the display name: diet_type uses "vegan", not "Vegan", as an array item like {"value": "vegan"}.
- An unfiltered summary returns at most 50 enum_values per attribute. Check enum_value_count and truncated_attributes before treating it as complete.
- Pass attributes=[...] to get uncapped values and schema details for those attributes. Targeted results fail rather than truncate when they exceed 512 KB.
- Use schema view for the full raw schema when it is at most 512 KB.
Watch out
- Product Type Definitions is a live Amazon call and requires Seller Central credentials for the marketplace, cached five minutes per seller, marketplace, product type, requirements, parentage, locale, and version.
- Raw schemas larger than 512 KB are refused. Targeted attribute details use the same ceiling; split large requests into smaller attributes lists.
write
create_listing
writeValidate or submit a full catalog listing contribution through the Listings Items API. The tool uses LISTING requirements, defaults to validation preview, and requires confirm=true plus an idempotency key to submit.
When to use
Create a product that is not already in Amazon’s catalog, or submit the full set of product facts and sales terms required for a catalog listing.
Parameters5
| Name | Type | Description |
|---|---|---|
sku* | string | Seller SKU for the listing (1-40 characters). |
product_type* | string | Amazon product type (e.g. SHIRT, LUGGAGE, HEALTH_PERSONAL_CARE). |
attributes* | object | Listing attributes object (max 50KB). Common keys: item_name, brand, bullet_point, product_description, externally_assigned_product_identifier (UPC/EAN), list_price, main_product_image_locator.Values follow Amazon attribute format. Check Amazon product type definitions for required attributes. |
confirm | boolean | Defaults to false for validation preview. Set true to submit the full listing creation. |
idempotency_key | string | Required when confirm=true. Reusing the same key blocks duplicate submissions. |
* required
Tips
- Use create_listing_offer instead when the ASIN already exists and you only need a seller SKU plus sales terms.
- Use get_listing_restrictions first to check the selected ASIN or product type for account-specific restrictions.
- Check the response for missing or malformed attributes before submission.
- Run preview first; submit with confirm=true and a unique idempotency_key only after Amazon returns a valid preview.
- The submission can be accepted for processing before the listing becomes buyable.
Watch out
- Do not use this full-catalog path merely to add a new SKU to an existing ASIN. It requires product facts that an offer-only submission does not.
create_listing_offer
writeCreate a seller SKU for an ASIN that already exists in Amazon’s catalog. The tool fixes productType to PRODUCT, submits LISTING_OFFER_ONLY sales terms, and never asks for title, brand, bullets, images, or other catalog facts.
When to use
Add a new seller SKU to an existing ASIN without making a full catalog contribution. Price and fulfillment are optional, so the SKU can be created inactive and completed later.
Parameters11
| Name | Type | Description |
|---|---|---|
sku* | string | New seller SKU to associate with the existing ASIN (1-40 characters). |
asin* | string | Existing 10-character ASIN in the active marketplace. |
condition_type | enum (new_new) | Amazon listing condition. |
condition_note | string | Optional note for the item’s condition, commonly used for non-new offers. |
price | number | Optional consumer price in the active marketplace currency. |
quantity | number | Optional seller-fulfilled quantity for the DEFAULT channel. Omit this for FBA. |
fulfillment_channel_code | string | Optional fulfillment channel. DEFAULT means seller fulfilled; Amazon-fulfilled values depend on marketplace and enrollment. |
lead_time_to_ship_max_days | number | Optional seller-fulfilled handling time for the DEFAULT channel (1-30 days). |
merchant_shipping_group | string | Optional shipping-template enum key from the PRODUCT Product Type Definition. Use the key, not the Seller Central display name. |
confirm | boolean | Defaults to false for Amazon validation preview. Set true to submit the offer-only SKU. |
idempotency_key | string | Required when confirm=true. Reusing the same key blocks duplicate submissions. |
* required
Tips
- Check listing restrictions for the ASIN and condition before submitting.
- The tool first proves that the SKU is unused and the ASIN exists in the selected marketplace.
- Amazon validation receives merchant_suggested_asin, condition_type, and any supplied price or fulfillment fields under LISTING_OFFER_ONLY.
- A confirmed submission performs one bounded Listings Items readback. The response separates Amazon acceptance from SKU-to-ASIN verification.
- Omit price and fulfillment when you intentionally want an inactive SKU; add those sales terms later with the dedicated price and quantity tools.
- For a new FBA SKU, set the Amazon-fulfilled channel during creation. Use convert_listings_to_fba only when the SKU already exists as seller fulfilled.
Watch out
- The tool will not replace or relink an existing SKU. Amazon-fulfilled channel codes and non-new condition requirements are marketplace-specific; Amazon validation is authoritative.
convert_listings_to_fba
writeConvert up to 25 existing seller-fulfilled SKUs to Fulfillment by Amazon through the Listings Items API. The tool checks current channels and ASIN-level FBA eligibility, runs Amazon validation preview, and requires confirm=true plus an idempotency key to submit.
When to use
Switch existing FBM listings to FBA before creating an inbound plan. Use create_listing_offer instead when the seller SKU does not exist yet.
Parameters3
| Name | Type | Description |
|---|---|---|
skus* | array | Existing seller SKUs to convert from the DEFAULT seller-fulfilled channel to the marketplace’s documented Amazon-fulfilled channel. Max 25 per call. |
confirm | boolean (false) | Runs eligibility checks and Amazon validation preview by default. Set true to submit every validated conversion. |
idempotency_key | string | Required when confirm=true. Reusing the same key blocks duplicate batch submissions. |
* required
Tips
- Preview reports each SKU’s ASIN, current channels, target channel, FBA eligibility, reason codes, and Amazon validation issues.
- The submitted patch adds the marketplace’s Amazon-fulfilled channel and deletes DEFAULT. A listing already in the requested FBA-only state returns a no-op.
- Confirmed rows receive one bounded Listings Items readback, so Amazon acceptance and observed fulfillment state remain separate facts.
- A transport failure is recorded as unknown and stops the remaining batch rather than expanding a potentially partial conversion.
Watch out
- Amazon rejects affected products when required battery or dangerous-goods attributes are missing. Amazon validation preview is authoritative.
- Conversion changes listing fulfillment availability only. It does not create an inbound plan, move inventory, or make FBA units sellable.
- The tool blocks listings with additional fulfillment channels and marketplaces without a documented fixed FBA channel rather than guessing.
update_listing
writeUpdate Amazon listing attributes by SKU through the Listings Items API. Resolves the marketplace-specific canonical product type, then runs Amazon validation preview before any submitted write.
When to use
Change listing content attributes such as title, Item Highlight, bullets, description, keywords, or images after reviewing the current Amazon listing state.
Parameters5
| Name | Type | Description |
|---|---|---|
sku* | string | Seller SKU for the listing to update. |
product_type | string | Optional product type candidate. Usually read from the current listing; the tool resolves Amazon’s canonical Product Type Definition for the marketplace before validation or submission. |
patches* | array | Attribute patches to submit. Each item includes attribute, op (add, replace, delete, or merge), and value unless op=delete. Use title_differentiation for Amazon Item Highlight. Max 20 attributes per call. |
confirm | boolean (false) | Runs Amazon validation preview by default. Set true to validate again, reserve the idempotency key, then submit the listing patch. |
idempotency_key | string | Required when confirm=true. Reusing the same key blocks duplicate listing updates. |
* required
Tips
- Call it once without confirm to review current values, the resolved product type, the exact patch set, and Amazon’s validation response.
- Use Amazon Listings Items API attribute format for values, such as item_name: [{ value: "New title", marketplace_id: "ATVPDKIKX0DER" }].
- For Item Highlight, use title_differentiation with the same array and object value shape. Amazon documents a 125-character limit; verify the current Product Type Definition for the marketplace and product type before submitting.
- Use a stable idempotency_key for the business action, such as listing-SKU-attribute-YYYYMMDD.
- Use update_price for pricing, update_inventory_quantity for seller-managed quantities, and convert_listings_to_fba for an FBM-to-FBA conversion.
Watch out
- item_highlights and product_highlights are not Listings Items API attributes. The tool rejects them rather than remapping because schemas can vary by product type.
- Amazon can return a legacy product type in a listing summary. The tool uses PTD’s marketplace-specific canonical value and reports both values when they differ.
- Amazon error 90251 describes the submitted patch request, not necessarily stored listing state. Conditional Product Type Definition rules can require a companion attribute in the same validation-preview patch set even when it is already stored; review the current value before including it in a confirmed submission.
- Requires Seller Central credentials and a Seller ID. Confirmed submissions are recorded in action history with pre-submit current values and submitted values.
update_price
writeSubmit Amazon consumer, scheduled sale, List Price (MSRP), and Amazon Business (B2B) price updates by SKU through the Listings Items API. Supports fixed-price or percent quantity discount tiers, runs Amazon validation preview by default, and requires confirm=true plus an idempotency key to submit.
When to use
Change base listing prices, schedule sales, set or update Amazon List Price (MSRP), or change Amazon Business prices and quantity discounts after reviewing the current listing state and confirming the exact listing patch submission.
Parameters3
| Name | Type | Description |
|---|---|---|
updates* | array | Price updates to submit. Each item includes sku plus at least one consumer, sale, List Price, or Amazon Business field. B2B fields are business_price, business_quantity_discount_plan (discount_type plus 1-5 ordered levels), and clear_business_quantity_discount_plan. list_price sets Amazon's List Price (MSRP) attribute. Max 25 SKUs per call. |
confirm | boolean (false) | Validation preview by default. Set true to submit price patches to Amazon. |
idempotency_key | string | Required when confirm=true. Reusing the same key blocks duplicate price update submissions. |
* required
Tips
- Call it once without confirm to preview exact SKUs, target prices or sale dates, and Amazon validation output.
- Use sale_price with sale_start_date and sale_end_date (YYYY-MM-DD) to schedule a temporary sale price.
- Use clear_sale_price=true to remove the scheduled discounted_price from the consumer offer.
- Set list_price to update Amazon's List Price (MSRP, the strikethrough reference price). It patches the top-level list_price attribute, which is distinct from the consumer price.
- For business_quantity_discount_plan, fixed values are per-unit prices in the marketplace currency; percent values are percentage discounts from the B2B price.
- Use clear_business_quantity_discount_plan=true to remove quantity tiers without deleting the B2B offer.
- Use a stable idempotency_key for the business action, such as price-SKU-YYYYMMDD.
- Set minimum and maximum seller allowed prices when you want Amazon-side bounds around the submitted consumer price.
- The tool patches the top-level purchasable_offer attribute using audience ALL for consumer pricing and audience B2B for Amazon Business pricing, and the top-level list_price attribute for List Price.
Watch out
- Requires Seller Central credentials and a Seller ID. Amazon Business fields require seller enrollment and product-type support for the selected marketplace; Amazon validation preview is authoritative. Confirmed submissions are capped at marketplace price bounds and recorded in action history as submitted values.
update_inventory_quantity
writeUpdate seller-fulfilled listing inventory quantities by SKU through the Listings Items API. Runs in preview mode by default and requires confirm=true plus an idempotency key to submit.
When to use
Change available listing quantities after reviewing current fulfillment availability, especially to mark seller-fulfilled SKUs in stock or out of stock.
Parameters3
| Name | Type | Description |
|---|---|---|
updates* | array | Seller-managed quantity updates to submit. Each item includes sku and quantity, plus optional seller-managed fulfillment_channel_code, lead_time_to_ship_max_days, and product_type. Amazon-fulfilled channels are rejected. Max 25 SKUs per call. |
confirm | boolean (false) | Preview by default. Set true to submit listing patches to Amazon. |
idempotency_key | string | Required when confirm=true. Reusing the same key blocks duplicate quantity updates. |
* required
Tips
- Call it once without confirm to preview current quantity, ASIN, product type, and the target quantity.
- Use quantity=0 to mark a seller-fulfilled SKU out of stock.
- Use a stable idempotency_key for the business action, such as inv-SKU-YYYYMMDD.
- The default fulfillment_channel_code is DEFAULT, the seller-fulfilled offer channel.
Watch out
- Requires Seller Central credentials and a Seller ID. Amazon-fulfilled channels do not accept seller-managed quantities; use convert_listings_to_fba for an FBM-to-FBA conversion. FBA warehouse stock remains controlled by Amazon inventory and inbound workflows.
live api
get_product_reviews
live apiSummarize Amazon Customer Feedback review topics for a child ASIN. Returns top positive and negative topics, mentions, occurrence percentages, star-rating impact, snippets, and subtopics.
When to use
Understand what customers praise or complain about for a product without reading individual reviews manually.
Parameters2
| Name | Type | Description |
|---|---|---|
asin* | string | Child ASIN to look up review topics for. |
sort_by | enum (MENTIONS) | Sort topics by MENTIONS or STAR_RATING_IMPACT. |
* required
Tips
- Use negative topics to group complaint themes by mentions, occurrence percentage, and star-rating impact.
- Use STAR_RATING_IMPACT when you care more about rating movement than mention volume.
- Compare child ASIN metrics against parent and browse-node metrics to see whether an issue is product-specific.
Watch out
- Amazon refreshes Customer Feedback data weekly. The API requires enough review volume and expects a child ASIN.
Related tools
hybrid
get_review_trends
hybridReturn Amazon Customer Feedback review-topic trends for a child ASIN from a live request or bounded stored snapshot history.
When to use
Read current monthly topic percentages from Amazon, or inspect older captured responses with explicit snapshot age and paused-source status.
Parameters7
| Name | Type | Description |
|---|---|---|
view | enum (live) | live makes a current Amazon request; history reads stored snapshots. |
asin* | string | Child ASIN to look up review topic trends for. |
snapshot_date | string | history only. Exact stored snapshot date (YYYY-MM-DD). |
start_date | string | history only. Stored snapshot start date (YYYY-MM-DD). Maximum 366 days. |
end_date | string | history only. Stored snapshot end date (YYYY-MM-DD). Maximum 366 days. |
limit | number (5) | history only. Snapshot page size (1-20); each snapshot can expand to several topic-month rows. |
include_raw_rows | boolean (true) | Set false to return a compact row preview. Defaults to true; large result sets are capped automatically to keep the response manageable. |
* required
Tips
- Use view="live" when current Amazon data is required.
- Use view="history" with snapshot_date for one captured response, or a bounded date range for several snapshots.
- Read snapshot_date, snapshot_age_days, freshness_state, and history_source before comparing stored rows.
Watch out
- Stored Customer Feedback ingestion is intentionally paused. History rows are stale snapshots and never claim to be current.
- The live API requires enough review volume and expects a child ASIN.