Skip to main content
Glama

Nova Amazon MCP Server

Server Details

Amazon Seller Central, Vendor Central and Ads data, profit-ready, for Claude, ChatGPT and any AI

Ownership verified
Status
Healthy
Uptime
43.5% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
nova-data-analytics/nova-amazon-mcp
GitHub Stars
0
Server Listing
MCP Nova Data Analytics
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 48 tools

Disambiguation3/5

The descriptions explicitly route between tools, but several analytics tools overlap in scope (query_metrics, find_movers, explain_movement, query_live, query_advertising, query_search_terms, query_sqp, query_dsp). Deprecated import_external_stock, import_stock_params and import_supplier_orders also overlap with import_supply_chain, making misselection more likely.

Naming Consistency5/5

All tools use lower snake_case with predictable verb_noun or action-resource patterns (list_*, get_*, query_*, import_*, set_*, update_*). Minor singular/plural variation such as create_events vs list_events is harmless and does not break the convention.

Tool Count2/5

48 tools is far above the well-scoped 3-15 range and creates a heavy selection surface for an agent. The Amazon seller analytics domain is broad, but the three deprecated import tools add avoidable clutter rather than earning their place.

Completeness4/5

The surface covers metrics, P&L, advertising, inventory, listings, promotions, reviews, SQP, DSP, Subscribe & Save, data imports and setup workflows, with read/write/import coverage across most domains. Minor gaps remain, such as no general order-history or product-search tool, no workspace-management tools, and events support without update/delete.

Publisher details

Operator
Nova Data Analytics SAS · Publisher source
Operator website
https://novadata.io
Vendor relationship
Independent
Privacy policy
Not provided
Restrictions
Paid plan from $49/month per Amazon account, with a 14-day free trial and no card required. Requires a Nova account with at least one Amazon Seller Central, Vendor Central or Ads account connected. Sign-in is OAuth with your Nova account; no custom OAuth app is needed. Listing content edits are limited to the Seller Central account owner and must be enabled for the workspace. · Publisher source

Available Tools

48 tools
create_eventsAInspect

Log one or several EVENTS on Nova — dated notes drawn on the charts so a later movement can be explained ("changed the A+ of B0…", "price +10% on amazon.es", "new PPC campaign", "launch"). The seller tells you what they did; log each change with the day it happened. One event covers MANY ASINs and marketplaces when it is the same change (one A+ rework on five ASINs = one event); distinct changes (different day, type or description) are separate entries of events, logged in ONE call. TWO-STEP: call WITHOUT commit; the server resolves each event's account, marketplaces and ASINs against the catalog (child or parent, product name, listed where — a mistyped ASIN shows here) and returns ONE preview with a confirmationToken; show it to the user and only after their approval call again with commitPayload plus commit:true and the token. type is the dashboard's vocabulary: content_change for title/bullets/images/video/A+, price_change for price/deals/coupons, ppc_change for campaigns/bids/budgets, product_launch, other. Check list_events first when the seller may already have logged it. Requires the OAuth connection (a workspace API token cannot write).

Inputs: events (required), commit, reason, confirmationToken.

describe_metricA
Read-only
Inspect

Get the full definition of a single metric (meaning, unit, grains it is valid at; for a Vendor Central (1P) metric, its basis; for a memo line beside the P&L, its group; for a Subscribe & Save metric, readingNote: how it reads over a period and when a day of it is final).

Inputs: key (required), reason.

explain_movementA
Read-only
Inspect

For one SKU, pull the causal signal bundle (traffic, conversion, price, buy box, promotions, ads, rank) for a period vs a baseline, so you can reason about WHY its sales moved. Returns each signal with value, comparison value and variance. 💱 CURRENCY: monetary values are served in the caller's Nova display currency when it is one of the organization's configured currencies (its primary or up to four secondary currencies), else in the organization's primary. In the response, currency is the code, currencyBasis says why (user_preference | organization | pinned) and currencyNotice, when present, MUST be relayed to the user. Quote the code; never assume a symbol from the marketplace. Pass currency to pin any configured code — e.g. to reproduce a figure the seller read on a dashboard set to another currency. 🏷️ 3P / 1P: an Amazon account sells through ONE programme: Seller Central (3P, channel SELLER: the seller sells its products to Amazon's customers) or Vendor Central (1P, channel VENDOR: Amazon BUYS the products from the vendor and resells them itself). On a Vendor Central read, the basis of units, sales and netSales is the answer's vendorTopLineNetReceived (said in its channelNote): when it is 1, units and sales of a Vendor Central row are Amazon's net received (what Amazon received from the vendor, net of what it returned, at its cost, on the day of the receipt: the Net received of the Vendor Central console) and netSales the net received less the quick-pay and early-payment discounts; what the vendor invoiced reads in vendorInvoiced; when it is 0, units and sales are what the vendor invoiced Amazon (its books, at the invoice date) and netSales the invoiced amount less Amazon's claims; Amazon's shelf (what it shipped to its customers, at its retail price, the latest days provisional, on ordered units) is read with vendorShippedUnits, vendorShippedRevenue and vendorShippedCogs. A vendor's profit is netProfit, the P&L's Net Profit: the P&L's top line (Amazon's net received when the answer's vendorTopLineNetReceived is 1, what the vendor invoiced Amazon when it is 0) less what Amazon takes off (its claims on the invoices, the discounts, the co-op, the chargebacks, the returns to vendor), the product cost and the ad spend. vendorShelfProfit is the result on what Amazon shipped, at the ship date: Amazon's shelf, the figure to compare products on, never added to the P&L. channel in list_accounts says which programme each account sells through. A call reads Seller Central, unless you pass channels=['VENDOR'] (do so only when the user asks about Vendor Central / 1P), the accounts of the call are all Vendor Central accounts, or you pass channels=['SELLER','VENDOR'] for All channels (when the user asks for the total across both programmes): Nova then reads both together as the app's All channels reading does, adding the seller's sales and the vendor's P&L top line. NEVER add 3P and 1P figures yourself: ask for All channels, or make one call per channel and present the two side by side, labelled 3P and 1P. When your scope holds a Vendor Central account the response says which channel it read ('SELLER', 'VENDOR' or 'ALL'), and channelNote what it read and what it left out; a metric the channel does not report (sessions, buy box, promotions on Vendor Central) comes back null with an unservedMetrics note, never 0. 📏 P&L RULES: the figures apply the P&L rules saved in Nova for this credential's organization, the P&L as the app shows it (a fee excluded from the fee total reads 0 on its line and is in no total; storage, long-term storage and paid services fees spread evenly over their month; margins on net sales; the FBM cost inferred from the shipping price; the VAT on Amazon fees booked as a cost; a share of refunded FBM units counted as put back on sale). When any rule is on, the answer lists them in pnlRules and carries pnlRulesNote, which you MUST relay once: a figure read without them (Seller Central, another tool) differs on every line a rule touches. Pass pnlRules="default" to read with no rule, as Amazon billed; the answer then says which rules the app applies. An organization that saved no rule reads as it always did, with neither key.

Inputs: to (required), sku (required), from (required), comparisonTo (required), +6 more.

find_moversA
Read-only
Inspect

Find the entities (SKUs by default) whose value moved the most for a metric between a period and a baseline. Use direction="down" to surface the biggest losers. This answers "which SKUs lost the most sales"; with tags (ids from list_tags) it ranks inside a brand or any tagged set. A metric of Amazon's S&S report is ranked only between two complete periods, past Amazon's delay and with S&S data every day: otherwise the answer has no rows, and notRanked and subscribeAndSaveNotice say why. 🧾 COST CATEGORIES: every cost has one of four categories (variable, product, oneOff, account; costCategory in list_metrics / describe_metric, and the totals orderCosts "Variable costs", productCosts, oneOffCosts, accountCosts). To compare products on their recurring economics, pass costCategories rather than subtracting lines yourself: the response then carries costCategories (what was counted) and costCategoriesNote, which you MUST relay, since the figures are no longer the P&L the app shows by default. 💱 CURRENCY: monetary values are served in the caller's Nova display currency when it is one of the organization's configured currencies (its primary or up to four secondary currencies), else in the organization's primary. In the response, currency is the code, currencyBasis says why (user_preference | organization | pinned) and currencyNotice, when present, MUST be relayed to the user. Quote the code; never assume a symbol from the marketplace. Pass currency to pin any configured code — e.g. to reproduce a figure the seller read on a dashboard set to another currency. 🏷️ 3P / 1P: an Amazon account sells through ONE programme: Seller Central (3P, channel SELLER: the seller sells its products to Amazon's customers) or Vendor Central (1P, channel VENDOR: Amazon BUYS the products from the vendor and resells them itself). On a Vendor Central read, the basis of units, sales and netSales is the answer's vendorTopLineNetReceived (said in its channelNote): when it is 1, units and sales of a Vendor Central row are Amazon's net received (what Amazon received from the vendor, net of what it returned, at its cost, on the day of the receipt: the Net received of the Vendor Central console) and netSales the net received less the quick-pay and early-payment discounts; what the vendor invoiced reads in vendorInvoiced; when it is 0, units and sales are what the vendor invoiced Amazon (its books, at the invoice date) and netSales the invoiced amount less Amazon's claims; Amazon's shelf (what it shipped to its customers, at its retail price, the latest days provisional, on ordered units) is read with vendorShippedUnits, vendorShippedRevenue and vendorShippedCogs. A vendor's profit is netProfit, the P&L's Net Profit: the P&L's top line (Amazon's net received when the answer's vendorTopLineNetReceived is 1, what the vendor invoiced Amazon when it is 0) less what Amazon takes off (its claims on the invoices, the discounts, the co-op, the chargebacks, the returns to vendor), the product cost and the ad spend. vendorShelfProfit is the result on what Amazon shipped, at the ship date: Amazon's shelf, the figure to compare products on, never added to the P&L. channel in list_accounts says which programme each account sells through. A call reads Seller Central, unless you pass channels=['VENDOR'] (do so only when the user asks about Vendor Central / 1P), the accounts of the call are all Vendor Central accounts, or you pass channels=['SELLER','VENDOR'] for All channels (when the user asks for the total across both programmes): Nova then reads both together as the app's All channels reading does, adding the seller's sales and the vendor's P&L top line. NEVER add 3P and 1P figures yourself: ask for All channels, or make one call per channel and present the two side by side, labelled 3P and 1P. When your scope holds a Vendor Central account the response says which channel it read ('SELLER', 'VENDOR' or 'ALL'), and channelNote what it read and what it left out; a metric the channel does not report (sessions, buy box, promotions on Vendor Central) comes back null with an unservedMetrics note, never 0. 📏 P&L RULES: the figures apply the P&L rules saved in Nova for this credential's organization, the P&L as the app shows it (a fee excluded from the fee total reads 0 on its line and is in no total; storage, long-term storage and paid services fees spread evenly over their month; margins on net sales; the FBM cost inferred from the shipping price; the VAT on Amazon fees booked as a cost; a share of refunded FBM units counted as put back on sale). When any rule is on, the answer lists them in pnlRules and carries pnlRulesNote, which you MUST relay once: a figure read without them (Seller Central, another tool) differs on every line a rule touches. Pass pnlRules="default" to read with no rule, as Amazon billed; the answer then says which rules the app applies. An organization that saved no rule reads as it always did, with neither key.

Inputs: to (required), from (required), metric (required), comparisonTo (required), +11 more.

get_cogs_worksheetA
Read-only
Inspect

One region's COGS worksheet — the import template as JSON: a row per (account, ASIN, SKU) product of the catalogue (products narrows the list like the Products filter of the COGS page) and per existing cost period/batch, with the CURRENT value (currentCogs null = no COGS yet). Use it to match a seller's source file to exact SKUs/ASINs before building import_cogs rows (match by SKU first, ASIN as fallback), and to read a SKU's full FIFO ladder before restating it. missingOnly=true keeps only rows without a value. Paginate with limit/offset (total is returned). Vendor Central (1P) products are listed too, each row then carrying its channel ('SELLER' = Seller Central, 'VENDOR' = Vendor Central).

Inputs: region (required), limit, offset, reason, +3 more.

get_fbm_worksheetA
Read-only
Inspect

One delivery zone's per-product FBM worksheet: a row per (account, ASIN, SKU) catalog product with its channel (isFbm), L24M sales and the CURRENT per-product override for that zone (currentCost null = the product falls on the seller's rate book). Use it to match a seller's per-product shipping file to exact SKUs/ASINs before building import_fbm_costs rows. Defaults to FBM products only (fbmOnly=false includes FBA); missingOnly=true keeps rows without an override. Paginate with limit/offset.

Inputs: zone (required), limit, offset, reason, +3 more.

get_listing_change_statusA
Read-only
Inspect

Seller Central only. Follow a listing change pushed from Nova: by batchId (the id update_listing_content returned) — every SKU with its Amazon status (SUBMITTED → ACCEPTED → STORED → PUBLISHED, or INVALID / REJECTED / NOT_REFLECTED / FAILED), its clocks (storedAt: Amazon holds the values; publishedAt: the public product page shows them, verified on the public catalogue; nextCheckAt: when Nova looks again, from 2 minutes to 72 hours after the change) and its issues, including why a stored value is not proven published (an attribute the public catalogue never shows, such as backend keywords, stays STORED with that reason) — or by marketplace + sku: the timeline of every attribute changed from Nova on that listing, with before/after, its status, its own publishedAt and its issues. It follows the changes sent through Nova only: an edit made in Seller Central is not listed, and a listing Nova never changed answers an empty changes with a note saying so.

Inputs: account (required), sku, reason, batchId, +1 more.

get_listing_contentA
Read-only
Inspect

Seller Central only (a Vendor Central account is refused by name: its content is changed in Vendor Central). Read the CURRENT editable content of up to 20 SKUs as Amazon holds it: title, bullets, description, backend keywords, and every other attribute the product type schema marks editable, flattened by column (item_name, bullet_point[1..10], item_dimensions.length.value…). account is optional: without it the SKUs are located across your accounts (one match = read; several = the matches are listed for you to pick). marketplaces takes country codes (FR), domains (amazon.fr) or ids; omitted = every marketplace the SKUs are listed on, with the values shared by all of them returned once under common. Only filled values are returned; emptyEditableAttributes names what the listing lacks; readOnlyAttributes cannot be changed through the API (Amazon's locks, and Nova's own: the offer — price, stock, shipping, tax, condition, offer images — is never written by Nova). Values are read from Amazon at call time (one call per SKU, asOf = the read time). This is the 'before' you MUST show the user before proposing any change.

Inputs: skus (required), reason, account, marketplaces.

get_setupA
Read-only
Inspect

Start here for any seller input: the setup surface of ONE domain, as the header of its Data Inputs page shows it. Read it before an import (target format, valid codes, import steps) and again after, to verify. domain: 'cogs' (cost of goods): default currency, each region's catalog SKU count and how many SOLD SKUs are missing COGS (profit overstated there), region inheritance policies, the valid region codes. soldSkusMissingCogs drops after an import. Covers Seller Central (3P) and Vendor Central (1P) accounts alike; when the scope holds a 1P account, vendorCentral lists it with the rules of a 1P cost (the vendor's OWN product cost, never Amazon's Shipped COGS; period-based only). Next: get_cogs_worksheet, import_cogs. 'fbm' (merchant-fulfilled shipping cost): per account, WHERE the seller ships (delivery countries with their share of FBM sales over 24 months, grouped in containers — Europe, North America, Far East — each led by its biggest destination), which countries have a shipping rate ('priced'), which read their container's rate ('container'), which fall on the rest-of-world rate ('row'), and which have NOTHING ('required' — the P&L cannot price those orders), plus packing/picking handling rates, per-product overrides and legacy rows; the zone/kind/rule vocabulary and how the P&L resolves a cost. Next: get_fbm_worksheet, import_fbm_zone_rates, import_fbm_costs. 'stock' (replenishment: reorder quantities, lead times, external / 3PL stock, supplier orders): per account, the stock regions it holds stock in, how many products are fully parameterised (the five reorder parameters — production lead time, transit from the factory to the warehouse, transit lead time to Amazon, target days of cover at Amazon and at the external location — resolved per product × region: product row → product 'ALL' row → seller default per region → seller default 'ALL' → fleet default (Nova's number for the warehouse, read from the seller's shipments and never typed; the Warehouse & 3PL page shows it in gold); a product whose five do not all resolve gets NO recommendation), the seller defaults, how many products carry an external (own warehouse / 3PL) count, how many supplier orders are open, and the last imports. Read it before query_inventory with includeReorder=true, to know whether the recommendations rest on entered parameters. Next: get_stock_worksheet, import_stock_params, import_external_stock, import_supplier_orders. 'supply_chain' (the TOP table of the Supply chain page): per account the production lead time; per warehouse its name and city, the territories it ships to with their transit to Amazon and target stock at Amazon, the target stock held at the warehouse and the transit from the factory, each number with its source ('yours' = the seller typed it, 'fleet default' = Nova's proposal from the fleet's shipments, the page's gold figure; beside a number the seller typed, fleetDefault is the proposal it replaces), how many products it holds and how many have a count; and the factory lines (goods straight from a country to a territory). Per warehouse also: key, the departure point the warehouse is named after, as query_inventory's departurePoints[].key names it; departurePoints, its other departure points (name, city, country, sharePct of the units shipped into its territories, shipments, units, status alive or past, factory) and otherPoints, the smaller ones folded (count, shipments, units); shippedToAmazonL12M, what it sent to Amazon over twelve months (units, shipments, onTheWay counts, and lastShipment, the date of its last plan, read from the name Seller Central gives a plan by default: null as soon as a plan of the window carries no readable date, since a seller who renames its plans would otherwise read its last default-named plan, months old, as its last shipment; undatedShipments counts those renamed plans, still listed by Amazon); onTheWay, its shipments on their way to Amazon (id, name, Amazon's status, phase, destination, units, unitsReceived, skus, created: null on a renamed plan); awdSharePct, the share of its units sent to Amazon through AWD, in %; freight, how its transit from the factory was read (zone, factory country, averageLotUnits, toConfirm when no factory shipment was read). Per account remote: the territories Amazon serves from another territory's stock. evidenceSince: the first day of the shipments read. Nova reads the warehouses from the seller's shipments: they are never configured. Next: set_stock_defaults (writes these numbers), import_supply_chain (takes a warehouse's name on its lines), get_supply_chain_products (the product lines). 'vat': PER ACCOUNT and per VAT region (EU, UK, Mexico, and OutsideEU read-only…), whether AMAZON prices the tax (VCS — then the seller's categories never reach the P&L) or the seller's product category does, with the count of SOLD SKUs Nova has no VAT for (profit wrong there); the account's default category; the full category referential (code + name, incl. the Nova codes A_NOVA_ZERO / A_NOVA_STANDARD / A_NOVA_REDUCED); how the P&L resolves VAT. Read the account you import for — verdicts are never pooled across accounts. Next: get_vat_worksheet, import_vat_categories, set_vat_default_category.

Inputs: domain (required), reason, accounts.

get_stock_worksheetA
Read-only
Inspect

One stock region's replenishment worksheet — the rows of the Data Inputs 'Stocks' page as JSON: a row per (account, ASIN) that holds or sells stock in the region, with the row's OWN values (own: what import_stock_params wrote for that product × region), what each of the five parameters RESOLVES to (resolved: product row → product 'ALL' row → account default for the region → account default 'ALL'), where each came from (source: asin_region | asin_all | seller_region | seller_all | null = nothing → no recommendation), paramsComplete, and the velocity / FBA stock next to it. region 'ALL' lists the product × 'ALL' rows (where a production lead time naturally lives). Use it to match a seller's lead-time file to exact ASINs before import_stock_params; missingOnly=true keeps the products that still resolve nothing for at least one parameter. Paginate with limit/offset.

Inputs: region (required), limit, offset, reason, +3 more.

get_supply_chain_productsA
Read-only
Inspect

The PRODUCT table of the Supply chain page ("Product overrides") as the page shows it (2026-10-22): one line per product × warehouse, the lines of the page's file, which import_supply_chain writes. Each line carries the account, the warehouse (its name as get_setup domain=supply_chain lists it, its region: the territory its count and orders are keyed on, its country), the ASIN with its name and SKU count, dailyUnitsSold (Daily units sold, summed over the territories the warehouse ships to), the count At warehouse / 3PL (warehouseUnits: 0 is a count, null = never counted; countedOn; countLocation 'own' or '3pl'), the OPEN supplier orders one by one (orders: reference, units, expectedOn, overdue = expected before today UTC, createdOn; import_supply_chain closes an order on its reference), On order (onOrderUnits, nextExpectedOn, overdueOrders) and numbers, the six numbers of the line (casePack, targetStockAtAmazonDays, targetStockAtWarehouseDays, transitToAmazonDays, transitToWarehouseDays, productionLeadTimeDays), each { value, source } by the page's rule: the product's own number ('product': its override, the page's black figure) → the warehouse's number saved in the Warehouse & 3PL setup ('warehouse': the page's grey inherited figure), or for the production lead time the account's ('account') → Nova's fleet default ('fleet default': read from the fleet's shipments, the page's gold figure) → null when nothing resolves (a case pack is the product's or nothing). On a line straight from the factory (warehouse.straightFromFactory, the page's « Straight from the factory ») there is no warehouse on the way: warehouseUnits is null, targetStockAtWarehouseDays and transitToWarehouseDays read { value: null, source: 'not applicable' } (the page's n/a; the recommendation reads them 0) and transitToAmazonDays is the whole trip, factory to sellable at Amazon. view reads the page's views: missing-count (no count at the warehouse; never a line straight from the factory), overdue-deliveries (an open order past its expected date), missing-lead-time (no production lead time typed on the product or on the account); counts gives the size of each view under the same search and filters. Use it to match a seller's file to the exact lines before import_supply_chain, and after, to verify. Paginate with limit/offset.

Inputs: skus, tags, view, asins, +6 more.

get_tacos_worksheetA
Read-only
Inspect

The TACOS targets worksheet of ONE workspace, the dashboard's bulk file as JSON: a row per child ASIN the workspace's accounts sell (sold in the last 24 months, or holding a target) with its name, parent ASIN, marketplaces, its last 30 days as the cockpit reads them, currentTarget (the target it is held against) and ownTarget (null = it follows the default). The L30D figures of a row come from one read of the cockpit's engine over period (the 30 days up to yesterday, both included), on the Seller Central accounts, with the organization's saved P&L rules: unitsL30D, salesL30D and adSpendL30D (the cockpit's Units, Sales and PPC Spend, the amounts in currency, the organization's), tacosL30D (adSpendL30D over salesL30D in percent, the PPC TACOS the Live page holds against the target; null without sales), marginBeforeAdsL30D and netMarginL30D (percent; on net sales when the organization's P&L policy says so). A null figure means the cockpit holds none for the product over those days (nothing sold nor spent), never 0. A TACOS target is the share of a product's sales the seller accepts to spend on ads: a WHOLE percent from 0 to 100 (12 = 12 %; 0 = no ads wanted), set per child ASIN for the whole ORGANIZATION, every account and marketplace alike. defaultTarget is the organization's default, what every product without its own target is held against (12 until the organization sets one: isDefaultSet false). A group (a parent ASIN, a marketplace, an account) stores no target: the Live page reads its products' targets weighted by their sales. Use it to match a seller's list to exact ASINs before building import_tacos_targets rows. One workspace in scope = implicit; several = pass workspace. Server-side pagination: limit/offset, total returned.

Inputs: limit, offset, reason, workspace.

get_tags_worksheetA
Read-only
Inspect

The product-tagging worksheet of ONE workspace — the template as JSON: the drawers (tag groups) the workspace has, and a row per (account, ASIN, SKU) catalog product with its CURRENT tags per drawer (tags: {Brand: ['Acme']}; predefined rule-based drawers are computed and never listed). Use it to match a seller's tagging file to exact SKUs/ASINs before building import_product_tags rows; drawer + untaggedOnly=true lists the products not yet tagged in that drawer. CHANNELS: lists Seller Central (3P) products by default; pass channels=['VENDOR'] for the Vendor Central (1P) products, or ['SELLER','VENDOR'] for both. Each row then carries channel; a 1P row is one product per (account, ASIN), tagged under its ASIN: its sku IS the ASIN (copy it as is into import_product_tags with channel 'VENDOR') and vendorCode is the code the 1P pages print. An ASIN sold on both channels is two rows, tagged apart. One workspace in scope = implicit; several = pass workspace. Paginate with limit/offset.

Inputs: limit, drawer, offset, reason, +3 more.

get_vat_worksheetA
Read-only
Inspect

One VAT region's worksheet — the same rows as the dashboard table: a row per (account, ASIN, SKU) sold product with its CURRENT category (null = none). missingOnly=true applies the dashboard's own definition of missing (on a region Amazon prices, a product with a measured treatment is not missing). Use it to match a seller's tax-class file to exact SKUs/ASINs before building import_vat_categories rows. Server-side pagination: limit/offset, total returned.

Inputs: region (required), limit, offset, reason, +2 more.

import_cogsA
Destructive
Inspect

Import COGS (cost of goods) rows for ONE seller account — TWO-STEP, never skip the preview: call WITHOUT commit first; the server validates and returns per-row warnings, a SKU-grain diff and a confirmationToken. SHOW the diff and warnings to the user and only after their explicit approval call again with the SAME account/mode/region/rows plus commit:true and the token. Mode 'merge' (default, safe for partial files) touches ONLY the keys you send: a 'fixed' row replaces the same period of its (asin, sku, region) and other periods survive; 'fifo' rows REPLACE that SKU's whole batch ladder — send the complete ladder (read it first with get_cogs_worksheet). Mode 'replace' wipes and restates every (account, region) present in rows — destructive with a partial payload, only for a full-region statement. Up to 2000 rows per call; for bigger files send several merge-mode calls. A Vendor Central (1P) account takes the vendor's own product cost, period-based only: 'fifo' rows are refused for it. Requires the OAuth connection (not a workspace API token) and the OWNER role.

Inputs: rows (required), account (required), mode, commit, +3 more.

import_external_stockA
Destructive
Inspect

DEPRECATED (2026-10-22): use import_supply_chain (warehouseUnits and countedOn per line); this tool stays for callers that still use it. Import the EXTERNAL STOCK of ONE account — the units the seller holds OUTSIDE Amazon (own warehouse or 3PL), per product × stock region: the fourth rung of the coverage ladder, what query_inventory returns as externalStock and counts in coverageWithExternal / recommendedOrderQty. A count is CURRENT state, not a movement: one row per (product, region) with the units on hand and the count date; 0 is a real count, an absent row means unknown (never 0). TWO-STEP like import_stock_params: preview WITHOUT commit (warnings + per-region diff + confirmationToken), show the user, then commit with the token. Mode 'merge' (default) upserts only the (ASIN, region) rows you send; 'replace' restates every (account, region) present in rows — a product absent from rows loses its count there. Up to 2000 rows per call. Requires the OAuth connection and the OWNER role.

Inputs: rows (required), account (required), mode, commit, +2 more.

import_fbm_costsA
Destructive
Inspect

Import PER-PRODUCT FBM cost overrides for ONE account: the exceptions to the rate book (a product that ships at its own cost to a zone). A row's zone is a delivery country ('DE') or 'ROW'; the override wins over the seller's zone rate for that destination. A row's rule says what its cost multiplies ('per_unit', 'per_parcel'); without one it follows the zone rate's rule. TWO-STEP like import_cogs: preview WITHOUT commit (warnings + SKU-grain diff + confirmationToken), show the user, then commit with the token. Mode 'merge' (default) upserts only the (asin, sku, zone, period) keys you send; 'replace' wipes and restates every (account, zone) present in rows, destructive with a partial payload. Up to 2000 rows per call. Requires the OAuth connection and the OWNER role.

Inputs: rows (required), account (required), mode, zone, +3 more.

import_fbm_zone_ratesA
Destructive
Inspect

Import the seller's FBM RATE BOOK for ONE account — the rates the P&L applies to merchant-fulfilled orders: 'shipping' per container ('EU_REGION', 'NA_REGION', 'FE_REGION': one rate for every country of it without a rate of its own), per delivery country ('DE', 'FR'…) or 'ROW' (every other country), and the handling costs 'packing' (per parcel) and 'picking' (per unit) on a container or on 'ALL'. This is the FIRST thing to set up: nothing is priced until a zone rate exists. TWO-STEP, never skip the preview: call WITHOUT commit; the server validates and returns per-line warnings, a diff (one line per zone|kind) and a confirmationToken; show them to the user and only after explicit approval call again with the SAME account/mode/rows plus commit:true and the token. Mode 'merge' (default) adds or updates only the (zone, kind, period) lines you send; 'replace' restates the WHOLE rate book — every line absent from rows is deleted. Requires the OAuth connection and the OWNER role.

Inputs: rows (required), account (required), mode, commit, +2 more.

import_product_tagsA
Destructive
Inspect

Tag products in ONE workspace — TWO-STEP like import_cogs: call WITHOUT commit; the server checks every product against the catalog, routes each drawer (existing local drawer, organization-shared drawer — assignments, plus the tags it lacks when the user is an organization owner (skipped otherwise) —, or a NEW local drawer created for you) and returns per-row warnings, a per-drawer diff, the BEFORE → AFTER of every (SKU, drawer) statement and a confirmationToken; SHOW them to the user, then commit with the SAME mode/rows plus commit:true and the token. mode is REQUIRED and says how a tags[drawer] cell is read: 'set' = the EXACT tags of this SKU in that drawer — tags not named are dropped, [] or null removes the SKU from the drawer; use it for a spreadsheet column or to move between exclusive tags (Summer → Winter). 'add' = these tags are ADDED to what the SKU already carries, nothing is ever removed; use it when the seller says 'add', 'also', 'tag these as'. Nothing outside the named cells changes (no drawer is deleted, unnamed products are untouched). VENDOR CENTRAL (1P): a 1P product is tagged under its ASIN — name it with the row get_tags_worksheet(channels=['VENDOR']) prints (sku = the ASIN) and channel 'VENDOR'; the tag then follows the product's 1P rows even after Amazon's vendor code changes. A row tags ONE product: an ASIN sold on both channels needs a 3P row (its SKU) and a 1P row (channel 'VENDOR') to be tagged on both. Tags then work as tags filters on the query tools and as the groupBy "tag" grain of query_metrics (list_tags gives their ids). One workspace in scope = implicit; several = pass workspace. Up to 2000 rows per call. Requires the OAuth connection.

Inputs: mode (required), rows (required), commit, reason, +2 more.

import_stock_paramsA
Destructive
Inspect

DEPRECATED (2026-10-22): use import_supply_chain, the Supply chain table as one line per product and warehouse, which changes only the lines it names; this tool stays for callers that still use it. Import the REORDER PARAMETERS of ONE account — per product × stock region (or 'ALL'): production lead time, transit lead time to Amazon, lead time from the factory to the warehouse (leadTimeToWarehouseDays), target days of cover at Amazon and at the external location, case pack. A product needs all five to RESOLVE (its own row → its 'ALL' row → the account defaults) before query_inventory recommends anything; a blank field resolves to the next rank, so set the account-wide values with set_stock_defaults and import here only the exceptions. A seller shipping straight from the factory to FBA has an external target of 0 and a to-warehouse lead time of 0, not blank. TWO-STEP, never skip the preview: call WITHOUT commit; the server validates (ASINs against the account's stocked products, regions, ranges) and returns per-row warnings, an ASIN-grain diff per (account, region) and a confirmationToken; show them to the user and only after explicit approval call again with the SAME account/mode/rows plus commit:true and the token. Mode 'merge' (default) touches only the (ASIN, region) rows you send, FIELD by field — a field you omit keeps its current value, null clears it; 'replace' restates every (account, region) present in rows whole — a product absent from rows loses its row there, an omitted field is blank. A row with nothing on it is refused (an import never clears a row). Up to 2000 rows per call. Requires the OAuth connection and the OWNER role.

Inputs: rows (required), account (required), mode, commit, +2 more.

import_supplier_ordersA
Destructive
Inspect

DEPRECATED (2026-10-22): use import_supply_chain (orderUnits, expectedOn, reference and status per line, one line per order); this tool stays for callers that still use it. Import the SUPPLIER ORDERS of ONE account — the seller's purchase orders on ITS supplier (not Amazon Vendor POs), per product × stock region: the fifth rung of the ladder, what query_inventory returns as onOrderUnits / nextExpectedAt and counts in coverageTotal / recommendedOrderQty. Only OPEN lines count; 'received' and 'cancelled' are history. TWO-STEP like import_stock_params: preview WITHOUT commit (warnings + per-region diff + confirmationToken), show the user, then commit with the token. Mode 'merge' (default): a line WITH a reference updates the line of the same (product, region, reference) — re-send it with status 'received' when the goods land —, the lines WITHOUT a reference restate the OPEN unreferenced book of their (product, region) — re-sending them is safe, received / cancelled lines untouched; 'replace' restates the OPEN order book of every (account, region) present in rows (open lines absent from rows are deleted, history untouched) and accepts status 'open' only. Up to 2000 rows per call. Requires the OAuth connection and the OWNER role.

Inputs: rows (required), account (required), mode, commit, +2 more.

import_supply_chainA
Destructive
Inspect

Import the PRODUCT table of the Supply chain page of ONE account — the same lines as the page's file (2026-10-22): one line per product × warehouse, carrying at most one supplier order (N open orders = N lines, the count and the six numbers repeated): the count at the warehouse / 3PL with its date, an order (units, expected date, PO reference, status), the case pack, the target stock at Amazon and at the warehouse, the transit to Amazon and to the warehouse, the production lead time. The payload changes the lines it names and NOTHING else: a field you omit keeps what is stored, null clears it (a count becomes unknown, an override is removed and the warehouse's number shows again), an order closes with status 'received' / 'cancelled' on its reference; the six numbers are the product's (its 'ALL' line), the same in every warehouse. The count's location and note are not here. On a line straight from the factory (get_supply_chain_products: warehouse.straightFromFactory) there is no warehouse: the count, the transit to the warehouse and the target there are not applied (a null there clears nothing) and the preview returns a notice for the row; put the whole trip, factory to sellable at Amazon, in leadTimeTransitDays. TWO-STEP, never skip the preview: call WITHOUT commit; the server validates (ASINs against the catalog, regions or warehouse names, ranges, dates) and returns per-row warnings, a per-warehouse diff (added lines with their values, changed lines before → after, removed, the warehouse's totals once written) and a confirmationToken; show them to the user and only after explicit approval call again with the SAME account/rows plus commit:true and the token. Up to 2000 rows per call. Requires the OAuth connection and the OWNER role.

Inputs: rows (required), account (required), commit, reason, +1 more.

import_tacos_targetsA
Destructive
Inspect

Set the TACOS target of products, TWO-STEP like import_vat_categories: call WITHOUT commit first; the server validates each row (an ASIN the workspace's accounts do not sell, or a target that is not a whole percent from 0 to 100, is warned and skipped: never written, and it never blocks the other rows) and returns per-row warnings, the diff (targets set, changed, cleared, unchanged) and a confirmationToken; SHOW them to the user and only after explicit approval call again with the SAME workspace/rows plus commit:true and the token. A TACOS target is the share of a product's sales the seller accepts to spend on ads: a WHOLE percent from 0 to 100 (12 = 12 %, never 0.12; 0 is a real target, 'no ads wanted'), held per child ASIN for the whole organization, every account and marketplace alike. target null CLEARS the product's own target: it follows the organization's default again (set_tacos_default_target). Only the ASINs you send are touched; several rows for one ASIN = the last wins. A committed change is announced to the Nova team, with your reason: say why. Up to 2000 rows per call. One workspace in scope = implicit; several = pass workspace. Requires the OAuth connection and the OWNER role.

Inputs: rows (required), commit, reason, workspace, +1 more.

import_vat_categoriesA
Destructive
Inspect

Import per-product VAT categories for ONE seller account — TWO-STEP like import_cogs: call WITHOUT commit first; the server validates (an unknown code, or a code of another region, rejects its row — warned, never written) and returns per-row warnings, a SKU-grain diff and a confirmationToken; SHOW them to the user and only after explicit approval call again with the SAME account/mode/region/rows plus commit:true and the token. Mode 'merge' (default, safe for partial files) touches ONLY the (asin, sku, region) keys you send — a category sets it, a null category CLEARS it. Mode 'replace' wipes and restates every (account, region) present in rows — destructive with a partial payload. Categories only matter on regions where Amazon does not price the tax (see get_setup domain=vat). Up to 2000 rows per call. Requires the OAuth connection and the OWNER role.

Inputs: rows (required), account (required), mode, commit, +3 more.

list_accountsA
Read-only
Inspect

List the seller's Amazon accounts you can query (id, name, region, channel, the marketplaces each sells on with their country code and domain, and the workspace(s) each belongs to). channel is the Amazon programme the account sells through: 'SELLER' = Seller Central (3P, the seller sells to Amazon's customers), 'VENDOR' = Vendor Central (1P, Amazon buys the products from the vendor and resells them). query_metrics, find_movers and explain_movement read Seller Central unless you pass channels=['VENDOR'], or channels=['SELLER','VENDOR'] for All channels; never add 3P and 1P figures yourself. Accounts can span several workspaces (e.g. an agency's separate clients) — use the workspaces field to tell them apart, and the accounts filter of the other tools to focus on one account or client.

Inputs: reason.

list_cost_inputsA
Read-only
Inspect

List the seller's CONFIGURED per-SKU input values — the raw values the seller entered (source of truth, not the aggregated metric). type selects which: 'cogs' (cost of goods, default), 'fbm' (merchant-fulfilment cost — the seller's rate book at level 'zone': shipping per delivery country or 'ROW', packing per parcel and picking per unit; then per-product rows at level 'sku'), or 'vat' (VAT product category). Use it to audit setup: spot placeholder / negative / implausible costs, cost entered per lot vs per unit (COGS quantity), wrong or missing VAT categories, or SKUs missing an input. Filter by skus to inspect specific products. To FIX missing or wrong COGS, use import_cogs (two-step, with user approval).

Inputs: skus, type, limit, reason, +1 more.

list_eventsA
Read-only
Inspect

The seller's EVENTS — the dated notes Nova draws on the charts to explain a movement: a price change, a content change (title, bullets, images, A+), a PPC change, a product launch, anything else the seller did. Read them when explaining a movement (what changed around that date?) and before create_event (is it already logged?). Filters: a date window, accounts, marketplaces, ASINs (child or parent, no need to know which), types, a text search. Newest first, 20 per page by default.

Inputs: to, from, asins, limit, +6 more.

list_metricsA
Read-only
Inspect

List the metrics Nova can report (key, label, unit type, whether higher is better). Call this first to discover valid metric keys for the other tools. When your accounts include a Vendor Central (1P) account, each metric also carries channels: the Amazon programmes it exists on, SELLER = Seller Central (3P), VENDOR = Vendor Central (1P); the Vendor Central metrics are listed too, each with its basis: 'sell-out' = Amazon's measures of what it shipped, 'sell-in' = the vendor's P&L (its top line Amazon's net received when the answer's vendorTopLineNetReceived is 1, what the vendor invoiced Amazon when it is 0), 'purchase-orders' = Amazon's purchase orders and receipts, 'stock' = the stock at Amazon. A memo line that reads beside the P&L carries group, the chapter it belongs to ('Tax position': the tax collected from customers, what Amazon remitted itself, what is left for the seller to remit; never part of net sales or net profit).

Inputs: reason.

list_negative_targetsA
Read-only
Inspect

The seller's NEGATIVE keywords and negative product targets — the traffic they deliberately blocked. Answers: is this query already negated, which campaigns block a brand, what did we exclude at the ad-group level. This is a LIST of rules, not metrics: a negation has no spend, no clicks and no period, so there is nothing here to sum or compare — for the spend a query wasted, use query_search_terms. The classic workflow is the pair: query_search_terms with metricFilters spend > X AND sales < 1 gives the negative CANDIDATES, then this tool tells you which of them are already negated. level is where the rule lives (campaign or ad_group), kind is what it blocks (keyword or product_target); a keyword negation carries keywordText + matchType, a product target carries expressionType + expressionValue (an ASIN or a brand id). Requires the ads entity snapshot to be built for the account. 🧭 SPONSORED PRODUCTS ONLY: no Sponsored Brands / Sponsored Display negative list is ingested yet, so adProducts accepts only sponsored_products (any other value is refused with a message saying so, never answered with the SP list under another name) and every row carries adProduct: 'sponsored_products'.

Inputs: q, kinds, limit, levels, +11 more.

list_tagsA
Read-only
Inspect

List "Your Filters" — the seller's own product classifications (custom drawers) and the tags inside each one, with the ids the other tools take: the tag ID a tags filter needs (query_metrics, find_movers, query_advertising, query_sqp, query_listing_health, query_bsr, query_inventory) and the drawer ID query_metrics groups by (groupBy "tag" + drawer — one row per tag of the drawer: sales, profit… per brand, per category). A drawer groups tags of one kind (e.g. "Brand" → "Private Label", "Wholesale"); type is "manual" when the seller assigned the SKUs by hand, or "predefined" when Nova computes membership from live data (Brand from Amazon's catalogue, FBA/FBM, hero, lifecycle, price tier). Call this to turn a name the user says ("my Private Label products") into the id to pass in tags — the filters take IDs, never names.

Inputs: reason.

query_advertisingA
Read-only
Inspect

Amazon advertising console — Sponsored Products + Sponsored Brands + Sponsored Brands Video + Sponsored Display + Full-Funnel campaigns — at the AD PRODUCT / PORTFOLIO / CAMPAIGN / AD GROUP / KEYWORD grain, the same pipeline as the app's PPC page. Answers: which keywords or campaigns waste spend (high spend, low sales, high acos), where to cut or raise bids, which keyword drives sales on a given ASIN/SKU, which placement (top of search vs product pages) the money goes to, where the money goes across ad products. groupBy takes the ad product (adProduct), an ad-structure grain (portfolio, campaign, adGroup, targetingType, targetingDetail, keyword), the placement grain, a product grain (childAsin, sku), or a TIME grain (day/week/month/quarter/year) for a series in ONE call. Keyword rows carry BOTH bids: bid is the target's current setting (falling back to the ad group default) and reportedBid is the bid Amazon reported on the last day of the window. Metric keys are a SEPARATE universe from list_metrics — use ONLY: spend, sales, sales14d, impressions, clicks, orders, units, units14d, acos, roas, cpc, ctr, cvr, marginBeforeAds, breakEvenAcos, profitAfterAds, spendWithoutSales, newToBrandOrders, newToBrandSales, newToBrandUnits, videoCompleteViews, viewableImpressions, brandedSearches, topOfSearchImpressionShare. 🏷️ THE BRAND KEYS (2026-09-17) are what only the Sponsored Brands / Brands Video / Display reports publish: newToBrandOrders / newToBrandSales / newToBrandUnits (14-day, click-attributed), videoCompleteViews (video rows only), viewableImpressions, brandedSearches; and topOfSearchImpressionShare, the share of top-of-search impressions the TARGET won (0-100, impression-weighted when rows are grouped): Sponsored Brands / Brands Video at any grain, and Sponsored Products at a TARGET grain only (groupBy keyword / targetingType / targetingDetail), from September 2026 (earlier days are null). ⚠️ It is NOT the console's 'IS | IR' (search-term impression share and rank): those ride on the KEYWORD rows as attributes, attrs.searchTermImpressionShare (0-100) and attrs.searchTermImpressionRank (1 = first), Amazon's numbers per account × marketplace × keyword TEXT over a rolling 30 days ending on attrs.searchTermImpressionAsOf (the latest daily snapshot, from 2026-09-18), independent of the period and NOT additive: never sum or average them; Sponsored Products keywords only, null on product targets and on every other ad product. Sponsored Products publishes none of the other six: with adProducts limited to sponsored_products (the default) they come back null on every row with an unservedMetrics note, never a 0 — pass the other ad products to read them; topOfSearchImpressionShare gets the same note when Sponsored Products is asked at a grain that is not a target grain. 💰 THE PROFIT KEYS answer 'is this advertising actually making money': marginBeforeAds is the P&L's Margin before Ads of the advertised products (exact per ASIN and marketplace, ad-sales-weighted elsewhere), under the organization's saved P&L rules and its own costs as the app's P&L page shows it (the answer then carries pnlRules and pnlRulesNote, to relay once), breakEvenAcos is the same number read against ACOS (spending above it loses money), profitAfterAds is (margin x ad sales) - ad spend, and spendWithoutSales is the spend on TARGETS with zero attributed sales over the whole period (not per day). Asking for any of them joins the P&L and resolves the attributed target_asin cut, so spend/sales on those rows become the attributed estimate rather than the exact advertised reading (it re-sums within 0.01%); omit them for the exact reading. They cannot be combined with the placement grain or a search-term filter (neither carries an ASIN or a target) and the call is refused with a message saying so. They are Sponsored Products / Sponsored Display keys: with sponsored_brands, sponsored_brands_video or full_funnel in adProducts they come back null on every row with an unservedMetrics note (per-ASIN Sponsored Brands is an allocation — query_metrics serves it; a Full-Funnel campaign's sales cover the whole brand), never a refusal; likewise the margin keys at a target grain with sponsored_display (no SD target → ASIN attribution). Sponsored Brands has no advertised-product report either, so childAsin / sku / parentAsin / tags with it are refused by name. ⚠️ Never sum or compare these with query_metrics' ad metrics (adSpend & co cover SP+SD+SB allocated to products, over the full history) — totals legitimately differ. ⚠️ Placement rows cannot be combined with a keyword or product dimension (Amazon reports placement per campaign only); such a combination is refused rather than silently emptied. Returns rows with value, comparison value and variance, plus the reporting currency. 🧭 AD PRODUCTS: the console serves Sponsored Products, Sponsored Brands, Sponsored Brands Video, Sponsored Display and Full-Funnel campaigns as DISJOINT blocks of rows — adProducts picks which (default ['sponsored_products'] until the fact serves the others; pass several to read them in ONE call, or groupBy='adProduct' to split the money by product). Each block is read from its own cut of the fact at its OWN attribution window: SP orders/sales/units are 7-day on a Seller Central account and 14-day on a Vendor Central account (each console's own window), SB and SBV 14-day, SD 14-day after a click OR a view, as Amazon's console counts them (the *14d metrics keep the clicks alone) — so never sum or compare sales, orders, ACOS or ROAS across products; spend is the ONE additive column across all of them, sponsored_brands + sponsored_brands_video (one report, split per row) the ONE additive pair, and sales14d / units14d the like-for-like 14-day reading. Sponsored Display has no search-term and no placement report (such a call is refused by name). Entity rows carry attrs.adProduct; it is null on a VALUE row (an ASIN, a placement, a targeting type, a search term) that folds two products. 🎯 FULL-FUNNEL ('full_funnel'): Amazon's Full-Funnel campaigns, ONE campaign serving on Amazon, off Amazon and on streaming video. Read them in total, over time, by campaign, or by product (childAsin / sku / parentAsin: the spend Amazon reports on no product, streaming video mostly, is one row with no ASIN, so the products re-sum to the campaign). They have no ad group, no keyword or target, no search term and no placement of this console: those grains and filters are refused by name. Their sales / orders / units are EVERY sale Amazon attributes to the campaign, the promoted products and the rest of the brand together, at a window Amazon does not state; sales14d / units14d, the profit keys, newToBrandUnits, viewableImpressions, brandedSearches and topOfSearchImpressionShare come back null with an unservedMetrics note, while newToBrandOrders, newToBrandSales and videoCompleteViews are served. A campaign Amazon's weekly report has not named yet reads its id without a name, and their current day is as of Nova's last hourly build, not the live stream. The P&L counts the same campaigns' cost as fullFunnelCost (query_metrics), where the part on no product is shared among the campaign's products. ⏳ HISTORY & ROUTING: this console route is built on Amazon's per-product advertising reports, so EACH AD PRODUCT HAS ITS OWN HISTORY FLOOR — the response's historyStartsAtByProduct is the first day held per product for the queried accounts (Sponsored Products ~95 days of report retention, Sponsored Brands / Brands Video 60 days, Sponsored Display 65–95 days; all backfilled ~60 days before the account's Ads connection; Full-Funnel from the first day Amazon's Full-Funnel report or its ads spend stream delivered for the account), and historyStartsAt is the earliest floor among the products you queried. Nothing before a product's floor is served for it (null, never zero spend). For ad TOTALS by account, product or period, and for ANY year-over-year or long-history comparison that needs no ad-product / portfolio / campaign / ad group / keyword / search-term / placement breakdown, use query_metrics instead (adSpend, sponsoredSales, organicSales, sponsoredAcos, sponsoredRoas, sponsoredTacos, impressions, clicks, costPerClick, clickThroughRate): it carries the whole ads history Nova holds for each account (from ~60 days before its Ads connection, complete from there; adsHistory gives the first day when a period starts earlier), Sponsored Products + Display + Brands allocated to products, plus the Full-Funnel campaigns. routingNotice, when present, says which route to prefer and where this one's history starts — relay its history part to the user whenever a requested period precedes a queried product's floor. 🕒 CURRENT DAY: on Seller Central accounts the current day is served live, from Amazon's hourly advertising stream, through the last hour Amazon has finished delivering (an hour that ended 45 minutes to two hours ago; the hour being delivered is left out, it holds its spend before its sales): all four ad products at the total, time, adProduct, portfolio and campaign grains, and Sponsored Products / Sponsored Display at the adGroup, childAsin and sku grains too. Attributed orders and sales of a recent day keep growing as Amazon attributes them. The keyword / targetingType / targetingDetail and placement grains, and Vendor Central accounts, follow Amazon's reports instead: their current day arrives hours later and can read lower than the live total — say so, never sum the two, and read a current-day total at a grain that is served live. ⏱ INTRADAY: the smallest grain of this tool is the DAY, and the current day is partial until it ends — its total against a whole earlier day is not a like-for-like comparison. For today by the hour, today against another day at the same time of day, the campaigns out of budget right now or the latest orders, use query_live. TODAY as this tool reads it: each marketplace on its own day; the orders within about a minute; the ad figures of an account through the last hour Amazon has finished delivering to THAT account, 45 minutes to two hours behind the clock — so today's TACOS and profit set sales to the minute against ad spend an hour behind, and are provisional. query_live reads today on ONE clock and holds an hour for every account once the first has it: over several time zones or several accounts its total for today can differ from this tool's, and neither is wrong. 💱 CURRENCY: monetary values are served in the caller's Nova display currency when it is one of the organization's configured currencies (its primary or up to four secondary currencies), else in the organization's primary. In the response, currency is the code, currencyBasis says why (user_preference | organization | pinned) and currencyNotice, when present, MUST be relayed to the user. Quote the code; never assume a symbol from the marketplace. Pass currency to pin any configured code — e.g. to reproduce a figure the seller read on a dashboard set to another currency.

Inputs: to (required), from (required), metrics (required), skus, +25 more.

query_bsrA
Read-only
Inspect

Best Seller Rank (BSR) for the seller's products — the CORRECT dedicated source that keeps the per-marketplace (category, rank) pair intact (a plain average would sever it). Use THIS for any BSR question; query_metrics does NOT serve BSR. granularity='latest' (default) returns the last observed rank in the window plus period-average main/sub category ranks (with an optional change vs a baseline window); a time grain (day/week/month/quarter/year) returns a rank time series. Lower rank = better. Products: pass the list matching groupBy (skus / childAsins / parentAsins) — ALL of them in ONE call, rows come back per product; never loop one call per ASIN. Without that list the tool reports the best sellers of the catalogue (limit, default 50, by sales of the last 90 days) and says so in scope; parentAsins with groupBy childAsin reports those parents' children. An empty result never means 'no BSR data': it is a filter that matches nothing, and the error says which.

Inputs: to (required), from (required), groupBy (required), skus, +11 more.

query_dspA
Read-only
Inspect

AMAZON DSP: the seller's Amazon DSP (Demand-Side Platform) advertising, Amazon's PROGRAMMATIC display and video ads bought in the DSP console: banners and video on Amazon's own sites and devices (its stores, Fire TV, Twitch...) and on third-party sites and apps, bought by audience rather than by keyword and billed per line item. It is NOT Sponsored ads: Sponsored Products / Brands / Display are the search-and-browse PPC that query_advertising serves. Separate budgets, separate consoles, separate attribution: a DSP conversion is counted post-click AND post-view over 14 days (a shopper who saw the ad and bought later counts), where PPC conversions are click-attributed. So NEVER add DSP spend to PPC spend, never add DSP sales to PPC sales, never compute one ACOS or ROAS across the two, and never compare a DSP ROAS with a PPC ROAS. In the app, the Advertising filter has three channels read side by side, PPC, Creator Connections and DSP; the P&L line 'Amazon DSP' (dspCost, under Advertising Cost) is this spend allocated to products, which query_metrics serves. Use query_dsp for anything about the DSP: what it costs, what it drives, which advertiser / order / line item / product / inventory / device / creative / audience / country, whether a line item is running; use query_advertising for Sponsored ads, query_metrics for advertising totals in the P&L. WHO IS READ: the DSP advertisers LINKED to the accounts of this call (Nova links each DSP advertiser to one of the seller's accounts, Seller Central or Vendor Central); accounts narrows them. History: Amazon's DSP reports reach back about 95 days, so an advertiser's figures start about 95 days before its connection to Nova; an earlier period comes back empty, never as zero spend. When no DSP advertiser is linked to the accounts, the answer says so (dspAdvertisers: 0, a notice, no rows): it is not an error, the seller does not run Amazon DSP through Nova. level (REQUIRED) picks the row: 'advertiser' (one per linked DSP advertiser), 'order' (a DSP campaign, with its budget, flight dates, pacing and Amazon's reach to date, household reach and frequency in attrs, as of the latest closed month), 'lineItem' (the grain Amazon bills, with its current status, type, budget and flight dates), 'product' (per ASIN, conversions only: Amazon reports no cost per ASIN), 'supplyFamily' and 'supplySource' (where the ads ran), 'device' (the screen), 'creative' (the ad asset), 'audience' (the segments reached: NOT additive, segments overlap), 'country' (where the ads served; the row with id '' is Unattributed). Each level is one of Amazon's DSP reports with its own metric universe, and the answer's levelNote says in one sentence what its rows are and what may be added across them: relay it whenever it qualifies the figures. Start at 'advertiser' or 'lineItem' for totals (no time grain here: a trend is several periods, one call each); the partitions (supply, device, creative, country) re-add to the line items; 'audience' is read beside them, never summed. Rows come biggest first on the first metric of the call unless sortBy says otherwise, and a row stays while it spent or sold over the period (sold, at 'product'), whatever metrics asks: the page's own population. METRICS are a SEPARATE universe from list_metrics and from query_advertising (same spellings, different meanings): spend (the total cost: supply cost plus every fee), supplyCost, fees, audienceFee, consoleFee, agencyFee, thirdPartyFees, impressions, viewableImpressions, viewabilityRate, clicks, ctr, ecpm, detailPageViews, dpvr, ecpdpv, addToCart, addToCartViews, addToCartClicks, atcr, purchases, unitsSold, sales (the PROMOTED products' conversions), totalPurchases, totalUnitsSold, totalSales (the promoted products plus the brand halo), purchaseRate, ecpp, newToBrandPurchases, newToBrandUnitsSold, newToBrandSales, newToBrandShare, totalNewToBrandPurchases, totalNewToBrandUnitsSold, totalNewToBrandShare, roas (promoted sales over spend), totalRoas (total sales over spend). Each level serves the subset its report carries: a key outside it is refused with the keys the level serves (no spend, impressions or ROAS at 'product'; no sales, units or halo at 'audience'; newToBrandSales and the four fee lines read on the 'advertiser', 'order' and 'lineItem' levels, the other reports carry fewer of them). Omit metrics for the level's core: spend, impressions, clicks, purchases, sales, totalSales, roas (the conversions at 'product'; no sales at 'audience'). FILTERS, on every level: dspAdvertiserIds, dspOrderIds, dspLineItemIds (the ids the upper levels return, strings), lineItemStatuses (the CURRENT status of the line items the rows belong to: RUNNING, PAUSED_BY_USER, ENDED, the DSP page's Status chip, Running / Paused / Ended), marketplaces. The level's own: asins and promoted ('product'), supplyFamilies and supplySources ('supplyFamily', 'supplySource'), deviceTypes ('device'), creativeIds and creativeTypes ('creative'), segmentIds, segmentClassCodes and targetingMethods ('audience'), countries ('country', '' allowed for the unattributed row). A filter of another level is refused by name. ANSWER: data rows with key (the level's type and id), attrs (the row's name and the level's attributes), metrics (value, and compared_value / variance with a comparison period); summary (total, mean and count over the whole selection before limit; the count only on 'audience'); level, levelNote, dspAdvertisers (the linked advertisers in scope), period and the reporting currency. 💱 CURRENCY: monetary values are served in the caller's Nova display currency when it is one of the organization's configured currencies (its primary or up to four secondary currencies), else in the organization's primary. In the response, currency is the code, currencyBasis says why (user_preference | organization | pinned) and currencyNotice, when present, MUST be relayed to the user. Quote the code; never assume a symbol from the marketplace. Pass currency to pin any configured code — e.g. to reproduce a figure the seller read on a dashboard set to another currency.

Inputs: to (required), from (required), level (required), asins, +25 more.

query_inbound_shipmentsA
Read-only
Inspect

FBA INBOUND SHIPMENTS — the app's Inventory › Inbound shipments panel, the same service the page calls (POST /v2/shipments): every shipment of the last 18 months at its CURRENT state, one record per shipment with its SKU lines (quantity shipped and received per SKU). Answers: what is on its way to Amazon, what Amazon has received so far, which closed shipments came up short (the reconciliation list), which SKU or ASIN has units in transit. category is the panel's own split: planned (WORKING / READY_TO_SHIP — units still with the seller, NOT inbound yet), in_progress (SHIPPED / IN_TRANSIT / DELIVERED / CHECKED_IN / RECEIVING with units still to receive), closed_incomplete (CLOSED and received < shipped), closed_complete (CLOSED and received >= shipped — Amazon sometimes receives more than declared). With sku or asin the category is judged on THAT product's lines, not on the whole shipment. ⚠️ Three things Amazon does not give, so neither does this tool: NO DATES (the inbound API exposes no shipped-at / received-at; fetchedAt is when Nova last read the shipment, nightly at 01:30 UTC, never a business date — within a category rows come in lifecycle order, and by missing units for closed_incomplete); marketplaceId is the marketplace Nova asked Amazon for, not where the shipment lives (the API ignores it) — read stockLocation / fcCountry, derived from the destination FC code; NO SHIPMENT COST anywhere (the inbound fees are query_metrics' fee keys, per SKU and day). isFromAwd flags an AWD → FBA replenishment leaving Amazon's own warehouse, not the seller's. Not a metrics tool: no period, no aggregation — read the counts off the records, or ask query_inventory for totalFbaIncoming / inboundUnits per SKU. SUMMARY (summary=true, 2026-10-22): the counters behind the Inventory page's « N shipments » pill, per product × stock location (POST /v2/shipments/summary), for the skus and / or asins given (a SKU on its own lines, an ASIN over all its SKUs), in stockLocation or in every location: openCount (shipments on their way: they left the seller and units are still to receive), awdCount (of them, the AWD → FBA replenishments), plannedCount (WORKING / READY_TO_SHIP, nothing left yet), incompleteCount (CLOSED with fewer units received than shipped), inboundUnits (the product's units still expected on the open ones) and missingUnits (its units never received on the closed ones); a product × location with none of these has no entry. At most 400 product × location pairs a call. On the list, dateFrom / dateTo bound fetchedAt and sortBy / sortOrder rank the shipments by one of the panel's columns.

Inputs: sku, asin, skus, asins, +14 more.

query_inventoryA
Read-only
Inspect

Current FBA inventory / stock health per SKU, per ASIN or per stock region — the dedicated source (same as the app's stock page), so quantities and days-of-inventory match the dashboard. Answers: what's about to run out (oosRiskFlag / low daysOfInventory), dead stock (withoutSales=true), reorder priorities (low projectedDaysOfInventory), how much stock is on hand, and whether a merchant-fulfilled (FBM) backup exists. Each row has totalFbaAvailable, totalFbaIncoming (= shipped + receiving), totalFbaInventory (= available + fcTransfer + reserved), afnReservedQuantity, fcTransferQuantity (units moving between Amazon FCs), totalFbaSellable (= available + fcTransfer, Amazon's On-hand and the daysOfInventory base, as Amazon's On-hand days of supply), salesVelocity (units/day, 30d), daysOfInventory, projectedDaysOfInventory (= sellable + reserved + inbound + the AWD stock and the units inbound to AWD when the product has AWD data, ÷ velocity: the Inventory page's « Days of supply · after inbound », Amazon's Total days of supply basis), oosRiskFlag (under 35 of those days), totalUnits30d, plus AMAZON'S INVENTORY STATES (the Manage FBA Inventory report's own columns): totalFbaInboundWorking (shipment plans created, nothing shipped: units still at the seller), totalFbaInboundShipped, totalFbaInboundReceiving, totalFbaUnsellable (Amazon's Unfulfillable: damaged, defective, expired — never sells), totalFbaResearching (misplaced units Amazon is confirming, 60 days at most), totalFbaSupply (Amazon's Total inventory supply for FBA = available + fcTransfer + reserved + unsellable + researching, the page's Total at Amazon), inboundUnits (the inbound the includeWorking switch shapes) and unitCog (the COGS per unit in the answer's currency, the organization's primary currency unless you pass currency: the SKU's own (a SKU with none that carries a stock it shares with other SKUs reads the COGS of one of those SKUs: one physical item, one cost), or on an ASIN row the average weighted by sellable units over the SKUs that have one; null = none) with unitCogSkus / unitCogSkusWithCog / unitCogUnitsWithCog (the SKUs behind the row, those priced, the sellable units they hold: read unitCog as partial when they differ), plus the FBM block: fbmAvailable (the quantity the seller declares on the SKU's FBM listing, active or not; null = no FBM listing; fbmIsPlaceholder flags ≥10k sentinels such as 99999), fbmListingStatus ('Active'; or, with includeInactiveFbm=true only, 'Inactive' when Amazon has suppressed every FBM listing of the row while units stay declared: fbmAvailable shows them, fbmListedQuantity counts them 0, so name the listing inactive before reading its units as stock for sale; null = no FBM listing. By default an inactive listing is not a listing of the read: its fbm* figures are null on the row and an FBM-only inactive SKU is not listed, as on the Inventory page unless the seller switches « Include inactive » on), fbmAvailablePoolGlobal (the SKU's quantity once across regions — a seller declares ONE quantity that every marketplace repeats), fbmListedQuantity (the FBM listed quantity, rule B 2026-10-23: the PRODUCT's declared quantity once per ASIN, read at the seller's home marketplace (the one where it keeps the most active FBM listings) since 2026-10-24: the largest over the product's SKUs there, 0 when the product is listed there with no active listing, and only for a product not listed there the largest over its other SKUs and regions; carried on one row and 0 on the product's other rows, so it is the one to total across SKUs and regions: a seller lists one product under several SKUs with the same figure on each, and summing them counted its warehouse once per SKU; an ASIN row's fbmAvailable is the largest of its SKUs in that region, never their sum), fbmListedStockValue (it × the latest COGS of its SKU), fbmSalesVelocity, fbmStockValue (in currency, like unitCog), fulfillmentChannel ('MFN' = an FBM-only SKU), plus the SUBSCRIBE & SAVE block from the daily offer snapshot: snsOffers / snsIneligibleOffers (the SKU's S&S offers in the region, and every one of them that is not ELIGIBLE, SUSPENDED included: an INELIGIBLE offer's subscriptions are cancelled, while a SUSPENDED offer is one Amazon has suspended from Subscribe & Save, and its existing subscriptions still count in Amazon's figures, so in snsActiveSubscriptions and the forecasts too; what Amazon does with their deliveries is not established, so state the suspension, never a consequence; query_subscribe_and_save section offers tells the two apart), snsActiveSubscriptions, snsForecastUnits30d / 60d / 90d (Amazon's projected subscriber deliveries — the demand a restock has to serve, to read next to daysOfInventory), snsDeliveries30dAtRisk (Amazon's at-risk count never includes a suspended offer), snsSnapshotDate; null = no S&S offer on that SKU (≠ 0 = an offer without subscribers). The rest of the block, from the offers themselves (null = no offer, or not built yet): snsEligibility, the row's state over its offers, the one rule of every Subscribe & Save surface (SUSPENDED when a suspended offer carries subscribers; else ELIGIBLE when an offer is ELIGIBLE or REPLENISHMENT_ONLY_ORDERING; else SUSPENDED when an offer is suspended at all; else INELIGIBLE when every offer is; at the ASIN grain over EVERY offer of the ASIN in the region, a SKU row over its own), snsSuspendedOffers and snsSuspendedOffersWithSubscribers (the suspended offers behind the row, and those of them that carry subscribers: an ELIGIBLE row with '1 suspended offer, no subscribers' is the difference), snsDeliveries30dPausedNonBuyable, snsDeliveries30dPausedPricing and snsDeliveries30dLowInventoryRisk (snsDeliveries30dAtRisk by Amazon's condition, in units: PAUSED because the offer is not buyable or for pricing, AT RISK still scheduled but threatened by low inventory; the three add up to snsDeliveries30dAtRisk), snsSellerFundedBaseDiscountMinPct / MaxPct and snsSellerFundedTieredDiscountMinPct / MaxPct (the discount the seller funds on the offers, in %, Amazon's base and tiered discounts: the lowest and the highest over the offers, equal when they agree, null when Amazon reported none); and in metadata, with includeReorder=true, snsPresent (any active subscription on the accounts and stock regions of the read, product filters aside; absent = not known) and snsUnstocked (the subscriptions on products with no stock row, and how many products). By default every figure is FBA-only and FBM-only SKUs are not listed; pass includeFbm=true to count the FBM stock in daysOfInventory / oosRiskFlag / the velocity and to list FBM-only SKUs — the 'days before a TOTAL stockout, FBM backup included' view. ⚠️ The non-*Pool quantities are per-SKU and MUST NOT be summed across SKUs (a shared FNSKU pool would double-count); use the *Pool columns when totalling. The answer carries currency, the code unitCog and fbmStockValue are in; page with limit and offset (pagination.total counts the rows). Tip: sortBy="daysOfInventory", sortOrder="asc" to surface what runs out first; sortBy="fulfillmentChannel", sortOrder="desc" lists the FBM-only SKUs first, then FBA SKUs that also carry an FBM listing (needs includeFbm=true for FBM-only SKUs to be listed at all). REPLENISHMENT (includeReorder=true): each row gains the reorder block — externalStock (units the seller holds outside Amazon, own warehouse / 3PL, per stock region; null = never entered), onOrderUnits / nextExpectedAt (open supplier orders), the resolved lead times and targets (leadTimeProductionDays, leadTimeToWarehouseDays, leadTimeTransitDays, targetDaysAmazon, targetDaysExternal, the inputs get_setup domain=stock reports), coverageWithExternal and coverageTotal (days of cover once the external stock, then the open orders, are shipped in), and recommendedOrderQty = max(0, salesVelocity × (lead times + targets) − everything already in the pipeline), rounded up to casePackQty, and priced as freight by recommendedOrderWeightKg / recommendedOrderVolumeCbm (kg and m³, from the package Amazon measured for the ASIN — packageWeightKg / packageVolumeCbm per unit; null when never measured, never 0); recoStatus says why it is null ('params_missing': the seller has not entered lead times / targets — nothing is assumed; 'no_velocity'; 'narf_echo'). needsReorder=true keeps the products to order now; paramsMissing=true the ones with no parameters. Attributes of the (region, ASIN): identical on every SKU of an ASIN, never sum them across SKUs. STOCK LOCATIONS (groupBy='stockRegion'): the Inventory page's "Stock locations" tiles instead of rows: one tile per stock region (territory) in data, and totals, the All locations tile. Each tile carries the units at Amazon by Amazon's states, deduplicated so that they add up across territories (a stock shared by several SKUs counts once, a NARF echo zero): unitsSellable (available + FC transfer, the units at Amazon the tile shows), unitsAvailable, unitsIncoming (shipped + receiving), unitsInboundWorking (shipment plans created, nothing shipped), unitsUnsellable, unitsResearching, unitsSupply (Amazon's total inventory supply, the page's Total at Amazon) and unitsFbm (the FBM listed quantity: what the seller declares on its FBM listings, counted once per product, read at the seller's home marketplace (the largest over the product's SKUs there; a product not listed there takes the largest over its other SKUs), in the territory of that row; declared, not counted by Amazon, so never in the totals nor in the shares); contribution (the territory's share of the sellable units, in %; the FBM listed quantity never enters it, whatever includeFbm); productCount (the products holding stock there); atRiskCount (the products flagged oosRiskFlag there, short even once the inbound lands: not additive across territories, All locations counts each product once); stockValue (Stock value = the sellable units × the latest COGS per unit, 0 without a COGS) and fbmStockValue (the FBM listed quantity × the latest COGS of its SKU), both in the answer's currency; and valuation, the stock at cost state by state that the tile's Stock value opens on (2026-10-22): { units, value } for sellable (= stockValue), reserved, inbound (shipped + receiving), unfulfillable, researching, awdOnhand, awdInbound, warehouse (the warehouse / 3PL counts at the product's COGS per unit; null without includeReorder) and fbm, each at the latest COGS per unit in currency, with unpricedUnits, the units no COGS prices, which no value counts. With includeReorder=true every tile adds unitsExternal (At warehouse / 3PL), unitsOnOrder (On order), needsReorderCount (the products to order now) and recommendedOrderUnits (Units to order). Every switch and filter of the rows applies, so the tiles describe the rows the same call lists; sortBy, sortOrder, limit and offset do not apply to tiles. stockRegions keeps the tiles of those territories, while totals stays All locations: the page's summary never narrows on a territory. STOCK AS OF A DATE (asOf=YYYY-MM-DD): the FBA stock the accounts held on that day instead of today's, read off the stock history: one row per stock region × SKU, each location at Amazon's latest FBA inventory report on or before the day, the way the Inventory page reads today's (a day between two reports carries the earlier one: reportDate names the report a row comes from, reportDates the oldest and the latest of the answer). A row carries sellerPartnerId, stockRegion, asin, sku, sellableUnits (available + FC transfer, the units the page shows at Amazon), availableUnits, reservedUnits, fcTransferUnits, inboundUnits (shipped + receiving), inboundWorkingUnits, unsellableUnits, researchingUnits, awdOnhandUnits and awdInboundUnits (reported on USA rows only, null elsewhere), unitCog (the COGS per unit in force on that day; null = none) and sellableValue (sellableUnits × unitCog, 0 without a COGS), amounts in the answer's currency (the organization's primary currency unless you pass currency) at the rate of that day. Unlike today's rows these quantities are deduplicated (a stock shared by several SKUs counts once, a NARF echo zero), so they add up across rows, SKUs, regions and accounts: totals sums every row the call keeps, one block per currency served, with skus (the rows) and products (the ASINs Amazon's report listed). coverage gives the first and the last day the history holds: a day before its first returns no rows, and a note says so. Only the scope exists on a past day: accounts, stockRegions, asins, skus, tags and q (a product gone from Amazon's report since still counts on the days it was listed). Nothing computed from today's read does, so with asOf the arguments includeFbm, includeWorking, includeInactiveFbm, includeReorder and withoutSales (switched on), oosRiskFlag, daysOfInventoryMin, daysOfInventoryMax, needsReorder, paramsMissing, coverageTotalMax, daysUntilReorderMax and marketplaces are refused, and so are groupBy 'asin' and 'stockRegion' (sum the rows, or pass stockRegions to read a territory's totals). sortBy then takes asin, sku, stockRegion, sellableUnits, sellableValue (the default, highest first), availableUnits, reservedUnits, inboundUnits, unsellableUnits or awdOnhandUnits. VENDOR CENTRAL (1P): this tool reads Seller Central stock only; a call whose accounts all sell through Vendor Central is refused, since the stock at Amazon is then Amazon's: read it with query_metrics, channels=['VENDOR'], and the metrics whose basis is 'stock' in list_metrics.

Inputs: q, asOf, skus, tags, +23 more.

query_listing_healthA
Read-only
Inspect

Current listing-health STATE per SKU — the same source as the app's Listing Health page, so statuses, suppression flags, and severity match the dashboard. Point-in-time entity state (NOT a metrics/date-range query — no from/to). Each row has: status, is_buyable, the per-issue flags (is_removed, is_suppressed, is_search_suppressed, is_attribute_suppressed, image_not_applied, is_compliance_risk, is_quality_issue, is_incomplete — a listing Amazon reports buyable is never is_suppressed: Amazon lists LISTING_SUPPRESSED on buyable, selling listings, so that notice counts as is_quality_issue instead; an action Amazon marks exempt never lights a flag), a severity_label + health_summary + the driving issue (top_issue_code/message/enforcement), the worst-wins alert_band (0 cash-loss · 1 degraded · 2 watch · 3 none), trailing-90d sales/units, the buy-box competition block (buy-box owner/price, hijack entrant, price undercut, contested), and a content block with the PUBLISHED catalog content (brand, manufacturer, productType, browse node id+name, variationTheme, titleHighlights (Amazon's item highlights, the second half of the new title format; null when the listing has none, and always null on Vendor Central), bulletPoints, productDescription, mainImageUrl full-size — NOT the small imageUrl render — imageCount, contentLanguage) plus the seller's SUBMITTED backendKeywords. Content gotchas: catalog fields are NULL until the catalog capture covers the ASIN (gate: contentFetchedAt=null); keywordsScanned=false means the Listings scope has not reached this SKU yet — backendKeywords NULL then means 'not looked at', never 'none written'. Answers: which listings are removed / suppressed / not buyable right now, what to fix first, who is losing the buy box, and content audits (missing bullets/description/backend keywords, image count, wrong content language). Filter by problems (per-issue checks), bands, or statuses; sort='severity' surfaces the worst listings first. CHANNELS: omit channels to read the Seller Central (3P) listings whenever the accounts of the call include a Seller Central account, else the Vendor Central (1P) ones (a vendor-only scope, or a Vendor Central account named alone in accounts); pass channels=['VENDOR'] for the Vendor Central (1P) listings, or ['SELLER','VENDOR'] for both in one list (next to a Seller Central account, a Vendor Central account is read only when VENDOR is asked for; a channel none of the accounts of the call sells on returns an empty list, not an error). Each row carries channel ('SELLER' = Seller Central, 'VENDOR' = Vendor Central). A Vendor Central row is one listing: its vendorProductIdentifier (the identifier Amazon shows in Vendor Central) in one marketplace under one vendorCode; the same ASIN under two vendor codes is two rows. The 90-day sales of a Vendor Central ASIN are Amazon's for the ASIN on its marketplace, not per listing: they are served once, on the ASIN's first row (sales90d, salesEur90d, units90d); its other rows read 0 and name in salesSharedWith the vendor codes of the row that carries them ([] on that row, on a Seller Central row and on an ASIN without sales), so a sum over the rows counts each ASIN once. statusLabel is the word the page shows for the status: 'Removed by Amazon' when Amazon removed the product from its catalogue (the Removed check), whatever the listings report says, 'Not in report' when the listings report no longer carries the SKU (outOfReportSince), else status; the statuses filter reads status. Its sku is the product SKU of the ASIN, as in the app's Copilot and Cockpit (the vendor's product code, or the ASIN when there is none), shared by the listings of that ASIN; skus filters on it. Vendor Central does not report five of the checks: not buyable, buy box lost, hijacker, price undercut and Incomplete never flag a Vendor Central row (Amazon is the seller: no offers block, offers is null, isFbm is null, status is Active or Inactive only). DATES AND CAUSES: statusSince is the day the listing's status last changed in Amazon's listings report (null when no change of status has been observed since the status history began on 2026-11-07); outOfReportSince is the day after the last listings report that carried the SKU, from which the listing is served Inactive (null while the report carries it). notBuyableCause says why a listing is not buyable, the first cause that applies: buyable_twin (another SKU of yours on the same ASIN and marketplace is buyable, so the product page still sells through it), out_of_report (the listing has dropped out of Amazon's listings report), no_stock (nothing to sell: no sellable FBA unit, or an FBM quantity of 0), amazon (Amazon blocks the listing: the top issue carries an enforcement action), inactive (the listing is Inactive in the report, most often closed by the seller), no_offer (the product page has no offer at all), offer_not_ours (the product page has offers, none of them yours), unknown (none of the above); null when the listing is buyable or has no signal. All three are null on Vendor Central rows: Amazon does not report them (isBuyable and flags.notBuyable are null there too, and the summary never claims buyable). CURRENCY: currency is the organization's reporting currency (the one its P&L is read in), never the marketplace's, on every row that has sales (a row without 90-day sales carries its marketplace currency); sales90d is the trailing 90 days converted day by day at each day's rate, where the Listing Health page shown in another display currency converts the whole 90 days at one average rate, so the two can differ by a few percent; offer prices carry their own offers.currency, the marketplace's. EMPTY ANSWERS carry a note: the accounts of the call that sell through another channel than the one read, or the ASINs / SKUs no listing matches; relay it rather than concluding that nothing is wrong.

Inputs: skus, sort, tags, asins, +10 more.

query_liveA
Read-only
Inspect

The CURRENT DAY as it happens — Nova's Live page: today's sales and ad spend HOUR BY HOUR, against a comparison day cut AT THE SAME TIME of day, the products and the campaigns that move, the campaigns out of budget, and the latest orders. Seller Central accounts. Use THIS tool when the question is about the pace of today, an hour of today, "right now", "so far today against yesterday at this time", a budget running out, or the last orders. view picks the read: "sales" = today's sales, units and orders, in total and by hour; "ads" = today's ad spend, clicks, impressions, attributed sales and orders, in total and by hour, with ACOS and TACOS (the sponsored ads of Amazon's hourly stream: Sponsored Products, Display and Brands, and the Full-Funnel campaigns, whose attributed sales are every sale Amazon attributes to the campaign, as the P&L's sponsored totals count them); "products" = the table of the products (or accounts, or marketplaces) by sales today, each against the comparison at the same time, with its change and its rank; "campaigns" = the table of the campaigns (or portfolios, or products) by ad spend today, each campaign with its daily budget, the share of it Amazon says is spent (campaign.budgetUsage.percent, null on a Full-Funnel campaign) and its portfolio's cap — budgetAlert: true returns only the campaigns out of budget or past 80 % of it; "orders" = the latest order lines, newest first, each with its product's name; "promotions" = how many PRODUCTS a promotion runs on right now, in two families as the page's two cards count them: Amazon deals and price discounts (the discount is in the price; with the products one starts on within 24 hours), and coupons and the seller's own promotions (the customer redeems them; with the products a deal or a price discount also runs on, and the promotions on the whole catalogue counted apart, since they name no product). For the coupons' family it also gives today's units of those products hour by hour and the units sold WITH the coupon or the promotion redeemed (redeemed), read on the order report: redeemed.through is where that report stops (about an hour behind the orders), redeemed.share is the redeemed units over the units the report holds to that same point (unitsSoldThrough), never over unitsSold to now; the redeemed units are a floor (a coupon on a Subscribe & Save delivery leaves no trace on the line). For the deals' family, dealsAndPriceDiscounts.today tells what the deals changed today, on the products that can be COMPARED only (productsCompared; unitsShareCompared is their share of the units every product in a deal sold today, and rule says what makes a product comparable): sales is what they sold today, salesAtUsualPrice the same units at each product's usual price, so discountGiven is the discount in the price; referenceDay.salesBySameTime is what an average day WITHOUT a deal or a price discount on the product sold by the same time (the product's own such days over the eight weeks before), so extraSales, salesRatio and unitsRatio are the uplift. It stops at through too, and it is a total over the products compared: never read it per product, and never as profit (no cost is in it). A coupon is no deal: a product under a coupon today and on its reference days carries it on both sides. registryLastReadAt is when Amazon's promotions registry was last read (every six hours). The promotions one by one, with their dates and terms: query_promotions. 🕒 ONE CLOCK: "today" is the calendar day on ONE clock — clock.timezone, the time zone of clock.marketplaceId (by default the marketplace with the most sales in scope; clockMarketplace names another). Every marketplace of the scope is read on that clock. query_metrics and query_advertising cut the day of each marketplace on its own clock: over several marketplaces their total for "today" is NOT this one. Quote a figure with its clock (clock.nowLocal) and never reconcile the two. 📊 COMPARISON: comparison.atSameTime is the comparison day cut at the same time of day — the figure to set today against; comparison.wholeDay is that day in full. change and every changePct are today against the same time; changePct is a RATIO (0.12 = +12 %), null when the comparison is 0. When change is null, changeNote says why: relay it, never compute a change yourself. hours is the day hour by hour on the clock (hour 0 = 00:00 to 00:59): today is null for an hour that has not started, and the hour in progress is partial. ⏱ FRESHNESS: an order arrives within about a minute; a recent line is priced by estimate until Amazon's report confirms it (isProvisional on a line, today.liveLines on the day). The ads are read through the last hour Amazon has finished delivering, through on the clock (the ads view) — an hour that ended 45 minutes to two hours ago, the same hour as the page's PPC tile, the P&L and query_advertising: the hour being delivered holds a part of its spend and not yet its sales, so it is left out; through is the END of the last hour read (through 04:00 = the hours 00:00 to 03:59, spelled in covers; the hour starting at 04:00 is not in the figures); it is null, with throughNote, while no hour of today is whole. acos and tacos are RATIOS (0.069 = 6.9 %) at that same cut, today and the comparison: ACOS is the spend over the sales Amazon attributes to the ads, TACOS the spend over the TOTAL sales (tacos.totalSales, the orders cut at through). tacos.comparison is null, with tacos.comparisonNote, when the ads and the orders do not hold the same days of the comparison (an hourly ad history that starts inside the days compared with): relay the note, never divide the two yourself. Quote these; never divide this view's spend by the sales of the sales view, which run to the minute: that TACOS is too low. Over SEVERAL ACCOUNTS this tool holds an hour for every account once Amazon has finished delivering it to the first, while query_metrics and query_advertising wait for each account's own delivery: for about ten minutes of an hour their total for today can be lower than this one. Both are right: say which tool a figure comes from, and never reconcile the two. freshness.latestHourReceivedAt is the latest hour Nova holds, which can still be in delivery: the figures stop at through, not there. Attributed ad sales keep growing for days. A campaign's budget figures (campaign.budgetAmount, budgetDay, budgetUsage, portfolioCap) are in the campaign's own currency, named beside them, never converted, on the campaign's own Amazon day. ↪ ROUTING: this tool reads TODAY only, as the Live page shows it. For today's total as the P&L and the Advertising page show it (each marketplace on its own day), for a day that is over or for a period of days, use query_metrics or query_advertising. 💱 CURRENCY: monetary values are served in the caller's Nova display currency when it is one of the organization's configured currencies (its primary or up to four secondary currencies), else in the organization's primary. In the response, currency is the code, currencyBasis says why (user_preference | organization | pinned) and currencyNotice, when present, MUST be relayed to the user. Quote the code; never assume a symbol from the marketplace. Pass currency to pin any configured code — e.g. to reproduce a figure the seller read on a dashboard set to another currency.

Inputs: view (required), skus, tags, limit, +13 more.

query_metricsA
Read-only
Inspect

Query the seller's metrics over a period, optionally grouped and compared to a baseline period. groupBy takes EITHER an entity grain (sku, childAsin, parentAsin, marketplace, sellerAccount), OR "tag" with drawer — one row per tag of one of the seller's own "Your Filters" drawers (list_tags): THE way to read sales, profit or any metric per BRAND, CATEGORY or supplier when the seller tagged the catalog —, OR a TIME grain (day, week, month, quarter, year). tags restricts any read to the SKUs carrying the given tags (ids from list_tags). Use a TIME grain to get a whole time series in ONE call — e.g. groupBy="month" from Jul to Jun returns all 12 monthly rows at once; never call this once per month. Entities batch the same way: for MANY SKUs/ASINs, pass the whole list (skus/childAsins/parentAsins) with an entity groupBy and read all the rows from ONE call — never loop one call per SKU or ASIN. Rank rows with sortBy+sortOrder (e.g. the top SKUs by netSales) and keep only rows meeting a threshold with metricFilters (e.g. SKUs with netProfit < 0) — both run server-side, so never fetch everything and filter yourself. Returns rows with value, comparison value and variance, plus the reporting currency. 📣 ADVERTISING TOTALS & HISTORY: this tool ALSO serves advertising at the account, product and period level — adSpend, sponsoredSales, organicSales, sponsoredAcos, sponsoredRoas, sponsoredTacos, impressions, clicks, costPerClick, clickThroughRate (Sponsored Products + Display + Brands, allocated to products, plus the Full-Funnel campaigns) — over the WHOLE ads history Nova holds for each account: from about 60 days before its Ads connection, complete from there (NOT a rolling 60-day window; adsHistory + adsHistoryNotice give the first day per account when a requested period starts earlier). Use THIS tool for ad totals, trends and year-over-year comparisons that need no ad-product / campaign / ad group / keyword / search-term / placement breakdown; query_advertising is the advertising CONSOLE for those breakdowns — Sponsored Products + Brands + Brands Video + Display + Full-Funnel as disjoint blocks, each at its own attribution window (SP 7-day on Seller Central and 14-day on Vendor Central, SB 14-day, SD 14-day after a click or a view, Full-Funnel every sale attributed to the campaign) and its own history floor (~60 days before the Ads connection at best). ⏱ INTRADAY: the smallest grain of this tool is the DAY, and the current day is partial until it ends — its total against a whole earlier day is not a like-for-like comparison. For today by the hour, today against another day at the same time of day, the campaigns out of budget right now or the latest orders, use query_live. TODAY as this tool reads it: each marketplace on its own day; the orders within about a minute; the ad figures of an account through the last hour Amazon has finished delivering to THAT account, 45 minutes to two hours behind the clock — so today's TACOS and profit set sales to the minute against ad spend an hour behind, and are provisional. query_live reads today on ONE clock and holds an hour for every account once the first has it: over several time zones or several accounts its total for today can differ from this tool's, and neither is wrong. ⚠️ CAVEATS: the response may carry cogsNotice (units sold with no COGS — profit and margins overstated; cogsCoverage always comes with a COGS-based metric), marketplaceNotice (the totals add up several marketplaces, e.g. US + CA + MX on a North America account, while Amazon screens show one), adsHistoryNotice (part of the period predates the account's ads data) and subscribeAndSaveNotice (Subscribe & Save figures of a period not final yet, or partly without S&S data). Each notice, when present, MUST be relayed to the user before the figures it qualifies. 🔁 SUBSCRIBE & SAVE (Seller Central only): shippedSubscriptionUnits (S&S Units), totalSubscriptionsRevenue (S&S Sales), lostSubscriptionsRevenue (S&S Sales Lost to Stockouts) and missedSubscriptionUnits (S&S Units Missed to Stockouts: Nova's estimate, in units, of the subscription deliveries Amazon missed for lack of stock, from Amazon's report; a floor when a day cannot be priced) are flows summed over the days, final 7 days after the day. subscribeAndSaveDiscount (S&S Discount Funded) is the discount the seller funded on subscriber orders, read from the order lines rather than from Amazon's S&S report, on the SKU of each order line, so neither the report's delay, its S&S data coverage nor the per-ASIN rule below applies to it. It moves with the order lines like productPromotions (Customer promotions), of which it is a part, served with its sign (never add the two): its last days rise as subscriber orders ship, and an order line can still be revised for weeks. On a line that also carried a coupon it is an estimate, usually low. Read it next to S&S Sales and never subtract it from S&S Sales, which is neither gross nor net of it. activeSubscriptions is a LEVEL, known 4 days after the day: the subscriptions active at the END of the period (each account and marketplace on its last day with S&S data in the period, added up across them), never added up over days nor averaged; in a time series each bucket is the level at its own end. salesPenetration (S&S Sales divided by product sales, both summed over the days that have S&S data only) and subscriptionsStockoutRate (S&S Sales Lost to Stockouts divided by S&S Sales plus that loss, both summed over the period, a day Amazon has not served counting on neither side) are ratios of sums, final 7 days after the day: never average daily or per-product values, ask for the period and the grouping you need. A period that ends within a figure's delay is PARTIAL: its figure is served flagged as partial, with the day it becomes final (its last day plus the delay); a period with no final day yet has no value: its figure is null (never the 0 or the partial amount Amazon has published so far), and a ranking or a threshold on it is refused. A period that holds days Nova has no S&S data for (before the account's S&S history, a day missing or held out, a feed that stopped) is INCOMPLETE, with no day to become final. When either period of a comparison is partial or incomplete, the S&S figure keeps its value but its change (variance, variance_percentage) is null. Never present a partial or incomplete figure as complete, nor compare it with another period: a partial or incomplete sum is too low, never a drop. Amazon reports S&S per ASIN, and Nova puts each ASIN's S&S figures on ONE of its SKUs (the first in alphabetical order): a sku or tag row, or a skus or tags filter, therefore holds the whole ASIN's figures or none of them, so read S&S per childAsin or coarser. The answer says which periods are partial or incomplete, and why, in subscribeAndSaveNotice (relay it) and subscribeAndSaveCoverage (per period state and finalBy for the delay and complete; per account and marketplace its days without data). The state of the programme and of each product today is query_subscribe_and_save. 🧾 COST CATEGORIES: every cost has one of four categories (variable, product, oneOff, account; costCategory in list_metrics / describe_metric, and the totals orderCosts "Variable costs", productCosts, oneOffCosts, accountCosts). To compare products on their recurring economics, pass costCategories rather than subtracting lines yourself: the response then carries costCategories (what was counted) and costCategoriesNote, which you MUST relay, since the figures are no longer the P&L the app shows by default. 💱 CURRENCY: monetary values are served in the caller's Nova display currency when it is one of the organization's configured currencies (its primary or up to four secondary currencies), else in the organization's primary. In the response, currency is the code, currencyBasis says why (user_preference | organization | pinned) and currencyNotice, when present, MUST be relayed to the user. Quote the code; never assume a symbol from the marketplace. Pass currency to pin any configured code — e.g. to reproduce a figure the seller read on a dashboard set to another currency. 🏷️ 3P / 1P: an Amazon account sells through ONE programme: Seller Central (3P, channel SELLER: the seller sells its products to Amazon's customers) or Vendor Central (1P, channel VENDOR: Amazon BUYS the products from the vendor and resells them itself). On a Vendor Central read, the basis of units, sales and netSales is the answer's vendorTopLineNetReceived (said in its channelNote): when it is 1, units and sales of a Vendor Central row are Amazon's net received (what Amazon received from the vendor, net of what it returned, at its cost, on the day of the receipt: the Net received of the Vendor Central console) and netSales the net received less the quick-pay and early-payment discounts; what the vendor invoiced reads in vendorInvoiced; when it is 0, units and sales are what the vendor invoiced Amazon (its books, at the invoice date) and netSales the invoiced amount less Amazon's claims; Amazon's shelf (what it shipped to its customers, at its retail price, the latest days provisional, on ordered units) is read with vendorShippedUnits, vendorShippedRevenue and vendorShippedCogs. A vendor's profit is netProfit, the P&L's Net Profit: the P&L's top line (Amazon's net received when the answer's vendorTopLineNetReceived is 1, what the vendor invoiced Amazon when it is 0) less what Amazon takes off (its claims on the invoices, the discounts, the co-op, the chargebacks, the returns to vendor), the product cost and the ad spend. vendorShelfProfit is the result on what Amazon shipped, at the ship date: Amazon's shelf, the figure to compare products on, never added to the P&L. channel in list_accounts says which programme each account sells through. A call reads Seller Central, unless you pass channels=['VENDOR'] (do so only when the user asks about Vendor Central / 1P), the accounts of the call are all Vendor Central accounts, or you pass channels=['SELLER','VENDOR'] for All channels (when the user asks for the total across both programmes): Nova then reads both together as the app's All channels reading does, adding the seller's sales and the vendor's P&L top line. NEVER add 3P and 1P figures yourself: ask for All channels, or make one call per channel and present the two side by side, labelled 3P and 1P. When your scope holds a Vendor Central account the response says which channel it read ('SELLER', 'VENDOR' or 'ALL'), and channelNote what it read and what it left out; a metric the channel does not report (sessions, buy box, promotions on Vendor Central) comes back null with an unservedMetrics note, never 0. 🧮 BASIS: basis picks which P&L the figures are. Omitted or "order" (what this tool always served): the order-based P&L, every amount at the day the order was purchased, the last days brought up to the live orders. "cash": the cash-based P&L, every amount at the day Amazon POSTED it, RELEASED postings only (a DEFERRED posting is a reserve, not cash) — the reading that ties to the settlement reports; no live overlay, Seller Central accounts only, and refused (never answered on the other basis) where the cash P&L is not enabled. Pick "cash" when the user speaks of settlements, payouts, disbursements, what Amazon paid, or reconciling with the bank; keep the order basis for sales performance. A cash answer carries basis: "cash" and a basisNote to relay once. What separates the two readings of a month is query_pnl_bridge. 📏 P&L RULES: the figures apply the P&L rules saved in Nova for this credential's organization, the P&L as the app shows it (a fee excluded from the fee total reads 0 on its line and is in no total; storage, long-term storage and paid services fees spread evenly over their month; margins on net sales; the FBM cost inferred from the shipping price; the VAT on Amazon fees booked as a cost; a share of refunded FBM units counted as put back on sale). When any rule is on, the answer lists them in pnlRules and carries pnlRulesNote, which you MUST relay once: a figure read without them (Seller Central, another tool) differs on every line a rule touches. Pass pnlRules="default" to read with no rule, as Amazon billed; the answer then says which rules the app applies. An organization that saved no rule reads as it always did, with neither key.

Inputs: to (required), from (required), metrics (required), skus, +24 more.

query_pnl_bridgeA
Read-only
Inspect

P&L BRIDGE: the order-based and the cash-based P&L of the same months side by side, and what separates them — for a finance team tying the commercial month (the orders) to the settlement month (the cash). view="month" (default): one row per calendar month over the accounts (and marketplaces) in scope with, for each P&L line (product sales, other sales, sales deductions, VAT, net sales, cost of goods, Amazon fees, FBM cost, PPC spend, DSP cost, net profit), the order reading (order), the cash reading (cash) and bridge = cash − order; sales splits the month's sales by TIMING on both sides (order sales whose principal was posted the same month / later / earlier / not yet; cash sales from lines purchased the same month / earlier months / later months / lines the order report does not know, of which sold to Amazon and without items) and gives the FX gap and the valuation gap of the same lines; fees does the same for the purchase-date fees (estimated at the order vs actually released). view="settlement": one row per settlement whose RELEASED postings fall in the months asked, most recent first, with the purchase months it pays (byPurchaseMonth, by marketplace and origin) and its own currency; settlementId narrows to one settlement and implies this view, and adds netProfitToDeposit: that settlement walked from the net profit of its cash P&L down to its deposit (the cost of goods Amazon never charged, the taxes that moved with the money, the reserves and other movements of the balance, what is left unallocated), in the settlement's own currency. Seller Central accounts only. 📐 HOW TO READ: amounts are as the marts store them — sales positive, costs and fees NEGATIVE (net profit = the sum of the lines); a positive bridge on a cost line means the cash reading spent less. Order basis = the day the order was purchased (what query_metrics serves by default); cash basis = the day Amazon POSTED the money, RELEASED postings only (what query_metrics serves with basis="cash"); a settlement = the RELEASED postings grouped under one settlement_id, the payout itself (the Transfer) excluded, so the sum of a settlement ties to the settlement report to the cent. Neither side has a live overlay: the current month is incomplete on both. Monetary values are in the organization's PRIMARY currency (currency in the response, the currency the marts are built in), never the caller's display preference; cashSalesLocal is in the settlement's own currency. total null = the bridge is not built in this environment; a null figure = not carried by the deployed bridge (unknown, never zero). Months are YYYY-MM.

Inputs: to (required), from (required), view, limit, +4 more.

query_promotionsA
Read-only
Inspect

PROMOTIONS RUNNING OR TO COME: the deals, coupons, price discounts and seller promotions of the accounts of the call that have started and not ended, or are scheduled, with the products each applies to. The same service as the promotions badge and modal of the app's Live page (POST /v2/promotions and /v2/promotions/summary), read off a table Nova rebuilds every hour from what Amazon lists. Answers: what is on promotion right now, what starts next and when, which products a deal or a coupon covers and at what price or discount, how a running deal or coupon is doing so far. type is one of DEAL (a Best Deal, a Lightning Deal or a Deal of the Day: subtype says which once Amazon's deal report lists the deal), COUPON (subtype STANDARD, SUBSCRIBE_AND_SAVE or REORDER_REWARDS), PRICE_DISCOUNT (a lower price on an offer for a period) and BASKET_BUILDING (a seller promotion: a discount or a free item for buying a quantity or an amount). state is decided at the time of the call (readAt) on the promotion's own dates: "running" = started and not ended, "upcoming" = not started yet; a promotion that has ended or was cancelled is not listed. Nova reads Amazon's list several times a day for a Seller Central account and once a day for a Vendor Central one: a promotion created since may not be listed yet. THE LIST (default): one record per promotion, the running ones first, then by start date. Each carries startAt / endAt (ISO instants, UTC; endAt null = Amazon gives no end), appliesTo ("products", or "whole_catalogue" for a seller promotion on every product of the account on that marketplace: it names no product, productCount is 0), its terms (percentOff in percentage points, 20 = 20 %; amountOff and promotionPrice in terms.currency; each a min / max over the products, equal when they all agree; the quantity or amount to buy to qualify), its budget when the promotion has one, its performance and its products (per product: the ASIN, the SKUs Amazon names for it, an empty list meaning every offer of the ASIN, its own price or discount, its own figures when Amazon reports them by product). A seller promotion can be TIERED, giving more for buying more (10 % from 2 units, 18 % from 3, 25 % from 5): terms.tiers then lists every step, the entry one first, each with the units (purchaseQuantityThreshold) or the amount (purchaseAmountThreshold, in terms.purchaseAmountCurrency) to buy to reach it and its percentOff; terms.percentOff runs from the entry step (min) to the top one (max), while the thresholds of terms and a product's own percentOff are the entry step's. tiers is empty when the promotion has one step. performance is the promotion's figures so far, CUMULATED SINCE IT STARTED and not a period; source says where they come from. A deal's and a coupon's are what Amazon reports: source names the Amazon report, asOf the day Nova read it. Amazon has no report for a seller promotion (BASKET_BUILDING): its source is "nova_order_lines", Nova's own count, on the day asOf, of the order lines that carry the promotion's trackingId since it started, cancelled orders left out. There unitsSold and salesAmount (the item price of those lines before the discount, shipping not included) are given for the promotion and for each product, 0 when no order has used the promotion yet; discountAmount is given only when none of those lines carries another promotion too (an order line has one discount for all the promotions applied to it), null otherwise. A price discount has no performance: Amazon has no report for it and an order line does not name it. null = no figure for that promotion (a price discount, a seller promotion that has not started, a deal or a coupon Amazon's report does not list yet), never zero; a null figure inside it is one the source does not carry. Amounts stay in the currency Amazon names, the marketplace's, never converted and never to be added across currencies. At most 100 products are listed under a promotion (productsTruncated says when there are more, productCount how many); when the call names products (childAsins, skus, parentAsins, tags) only THOSE products are listed under each promotion. pagination.total counts the promotions the filters keep. SUMMARY (summary=true): the counts behind the page's badge, per row of groupBy: running, upcoming, the same by types, and wholeCatalogue (how many of them are promotions on the whole catalogue, counted on every listed product of the account). A row's count is the number of DISTINCT promotions that apply to at least one of its products, so a parent's count is never the sum of its variants' (a coupon on three variants counts once on their parent). Only the rows with a promotion come back. groupBy sellerAccount or marketplace counts every account or marketplace of the call; a product grouping (childAsin, the default; sku; parentAsin) counts the rows named in keys, at most 200. Not a metrics tool: no period and no cost. What the promotions cost over a period (the discounts given on the orders) is a P&L line of query_metrics; what a product sold today is query_live. Not in this tool: the Subscribe & Save programme's own discount (query_subscribe_and_save; a Subscribe & Save coupon is a COUPON here), Brand Tailored promotions, Vine, and the advertising campaigns (query_advertising).

Inputs: keys, skus, tags, limit, +11 more.

query_reviewsA
Read-only
Inspect

Amazon REVIEWS and RATINGS of the seller's products, per ASIN and marketplace (Amazon Data Kiosk): the reviews received over a period, the critical ones (3 stars or less), the star rating and the ratings count Amazon displays, and a review rate. The same route as the app's Reviews columns and modal, on the Seller Central (3P) accounts of the call. Metric keys are their OWN universe, not list_metrics keys: reviews, critical_reviews, critical_review_share, review_units, review_rate, rating, ratings, rating_week_end, rating_marketplace (describe_metric defines each). ⚠️ READ BEFORE ANSWERING. (1) The COUNTS (reviews, critical_reviews, critical_review_share, review_units, review_rate) exist only on the marketplaces where Amazon serves them: US, CA, MX, BR. Everywhere else, Europe included, they are null (n/a), never 0. (2) A review belongs to the ASIN: every new rating from ANY buyer of the ASIN, written or not (the product page lists the written ones only), not only this seller's buyers. So there is no SKU grain (a SKU or tag filter reads its ASIN's reviews), and two seller accounts carrying one ASIN carry the same reviews: never add up the rows of groupBy sellerAccount yourself, summary.total counts each ASIN once. (3) Amazon serves a day of reviews about 3 days late, and its last served day is still filling: the answer's reviews_served_from and reviews_served_to are the first and last days served, reviews_complete_to the last complete one. Compare periods, or compute a pace or a rate, over complete days only. In a series a bucket without a review reads null: no review on a served day, not known on the others. (4) rating and ratings are the state the product page displays (ratings is Amazon's count for the ASIN worldwide since its launch, not the period's), read at the period end, never a period total. A row covering several marketplaces reads its top-selling one (rating_marketplace), never a blend; never add ratings up across rows. Amazon keeps no rating history: Nova's is its own reads, which started on 2026-10-01 (per week, the first document closes on 2026-09-26); a bucket before the first read is empty, never 0. (5) review_rate = the ASIN's reviews (all buyers) per 100 units sold by THIS account (review_units): meaningful only where the seller is the ASIN's only seller (its own brand), meaningless on a reseller's shared ASINs (it can exceed 100). (6) NO comparison mode: call once per period. (7) groupBy is EITHER an entity grain (parentAsin, marketplaceParentAsin, childAsin, marketplace, sellerAccount) OR a time grain (day, week, month), never both: for one product's series, filter on it and group by the grain. Per day, week or month: the flows (reviews, critical_reviews, critical_review_share). Per day (as read each day) or week (Amazon's week documents), never month, and in a call of their own: rating, ratings, rating_week_end. Never per time bucket: review_units, review_rate, rating_marketplace. A series comes whole and in date order, one row per bucket: no sortBy, limit or offset, and 1000 buckets at most (over a long period, group by week or month). 🔒 HISTORY: every plan reads the whole history, except a read of review_units or review_rate by an organization on its free trial (no subscription yet, an abandoned checkout included, or no active subscription while its 14-day trial still runs): nothing before its floor is served then, its reviews included, and the answer carries dataFloor, that ISO day, when Nova can state the floor that applied. A paying plan, and a plan cancelled after its trial ended, read the whole history. Vendor Central (1P) accounts have no reviews here: Amazon serves vendors no rating and no review count.

Inputs: period (required), metrics (required), limit, offset, +6 more.

query_search_termsA
Read-only
Inspect

The actual customer SEARCH QUERIES behind Sponsored Products and Sponsored Brands spend — the search-term report, same pipeline as the app (Sponsored Display and Full-Funnel have no search-term report: asking for either is refused by name). Answers: what customers really type before clicking an ad, negative-keyword candidates (queries with spend and zero sales), auto-campaign discoveries worth promoting to exact match. groupBy="searchTerm" is the main drill-down; the ad product (adProduct), ad-structure grains (portfolio/campaign/adGroup/targetingType/targetingDetail/keyword) and TIME grains also work. Metric universe = the ads keys MINUS impressions/ctr (biased at this grain, rejected) and MINUS the seven brand keys (newToBrand*, videoCompleteViews, viewableImpressions, brandedSearches, topOfSearchImpressionShare — the search-term reports carry none of them) and MINUS the four profit keys (this grain carries no ASIN, so there is no product margin to price a query at — use query_advertising for those): spend, sales, sales14d, clicks, orders, units, units14d, acos, roas, cpc, cvr. NO product (ASIN/SKU) dimension or filter exists here — the search-term report carries no ASIN attribution; for per-product ads use query_advertising. Rows with search term '*' are PDP placements with no typed query. ⚠️ groupBy="searchTerm" serves CLICKED QUERIES ONLY: a query with 0 clicks over the requested period is not served, and rows, summary.count and summary.total all follow that rule (Amazon also emits 0-click / 0-spend rows carrying attribution-window sales; they used to top every ACOS-ascending sort at a fake 0.0%). It is a PERIOD rule, not a daily one — a query clicked on one day keeps the sales its other days attribute. ACOS is null, never 0, when nothing was spent. 🚫 Each searchTerm row carries attrs.negatedLevel ('campaign' | 'ad_group' | null): a keyword negative on that EXACT text already blocking the traffic THIS row is made of — a campaign the row spent in, or an ad group it spent in. A negative in a SIBLING ad group is NOT reported: the query is still costing money where you are looking. Expect it to be null almost everywhere and do not read that as "nothing is blocked" — a negative that works stops the query being served, so it leaves this report entirely; what lights up is a query negated DURING the period. For "have I ever blocked this anywhere", use list_negative_targets with q = the term. ⚠️ Never cross-sum with query_metrics' ad metrics. 🧭 AD PRODUCTS: the console serves Sponsored Products, Sponsored Brands, Sponsored Brands Video, Sponsored Display and Full-Funnel campaigns as DISJOINT blocks of rows — adProducts picks which (default ['sponsored_products'] until the fact serves the others; pass several to read them in ONE call, or groupBy='adProduct' to split the money by product). Each block is read from its own cut of the fact at its OWN attribution window: SP orders/sales/units are 7-day on a Seller Central account and 14-day on a Vendor Central account (each console's own window), SB and SBV 14-day, SD 14-day after a click OR a view, as Amazon's console counts them (the *14d metrics keep the clicks alone) — so never sum or compare sales, orders, ACOS or ROAS across products; spend is the ONE additive column across all of them, sponsored_brands + sponsored_brands_video (one report, split per row) the ONE additive pair, and sales14d / units14d the like-for-like 14-day reading. Sponsored Display has no search-term and no placement report (such a call is refused by name). Entity rows carry attrs.adProduct; it is null on a VALUE row (an ASIN, a placement, a targeting type, a search term) that folds two products. 🎯 FULL-FUNNEL ('full_funnel'): Amazon's Full-Funnel campaigns, ONE campaign serving on Amazon, off Amazon and on streaming video. Read them in total, over time, by campaign, or by product (childAsin / sku / parentAsin: the spend Amazon reports on no product, streaming video mostly, is one row with no ASIN, so the products re-sum to the campaign). They have no ad group, no keyword or target, no search term and no placement of this console: those grains and filters are refused by name. Their sales / orders / units are EVERY sale Amazon attributes to the campaign, the promoted products and the rest of the brand together, at a window Amazon does not state; sales14d / units14d, the profit keys, newToBrandUnits, viewableImpressions, brandedSearches and topOfSearchImpressionShare come back null with an unservedMetrics note, while newToBrandOrders, newToBrandSales and videoCompleteViews are served. A campaign Amazon's weekly report has not named yet reads its id without a name, and their current day is as of Nova's last hourly build, not the live stream. The P&L counts the same campaigns' cost as fullFunnelCost (query_metrics), where the part on no product is shared among the campaign's products. 💱 CURRENCY: monetary values are served in the caller's Nova display currency when it is one of the organization's configured currencies (its primary or up to four secondary currencies), else in the organization's primary. In the response, currency is the code, currencyBasis says why (user_preference | organization | pinned) and currencyNotice, when present, MUST be relayed to the user. Quote the code; never assume a symbol from the marketplace. Pass currency to pin any configured code — e.g. to reproduce a figure the seller read on a dashboard set to another currency.

Inputs: to (required), from (required), metrics (required), limit, +21 more.

query_sqpA
Read-only
Inspect

Amazon SEARCH QUERY PERFORMANCE (Brand Analytics), curated — what shoppers TYPE on Amazon, the whole market's funnel on each query, and your slice of it. ORGANIC demand: this is not ads, and not query_search_terms (that one is what people typed before clicking YOUR ad; this is every seller's behaviour on the query). Answers: which keywords grow or shrink my market, where I lose share, which high-volume queries I am absent from, whether competitors take my brand, do I convert better than the market, am I priced above it. Two vocabularies: market_* = all sellers on that query, your_* = this product. ⏱ FIXED CALENDAR PERIODS: grain is REQUIRED ('week' | 'month'); omit from/to and you get the LATEST COMPLETE period, which is what you almost always want. The response echoes the period actually served: period.from/to are period STARTS (the mart key — read alone they look like one day), and period.covers is the SAME period in calendar DAYS (an SQP week is SUNDAY→Saturday, not an ISO Monday week; a month 1st→last). Weekly runs ~10 days behind, monthly ~7 WEEKS behind, so when crossing with query_metrics / query_advertising / query_search_terms you MUST pass EXACTLY period.covers.from and period.covers.to as their from/to — never 'this month', never period.from/to, and never a weekly series from those tools (their weeks start on Monday and will not line up with SQP weeks). 🔒 HISTORY DEPTH: on a trial plan the response carries dataFloor, an ISO day — NOTHING before it was served, whatever the seller's real history holds, so absence below that day means 'withheld by the plan', never 'no demand'. The field is ABSENT when nothing was withheld. Say so instead of concluding a keyword is new or a market collapsed. 📊 COMPARISON IS A METRIC, not a mode: use search_volume_yoy_pct (month) or search_volume_wow_pct (week) — they are like-for-like, computed only over keywords present in BOTH periods; comparing period totals reads +34% where the truth is -3%. Read comparable_keywords / comparable_share to see how solid it is; the metric is null below the reliability floor. ⚠️ DO NOT SUM market_* VALUES ACROSS ROWS YOURSELF: a query's volume is repeated on every parent ASIN that ranks on it, so adding rows double counts (measured x2.4). The summary block is already de-duplicated — use it. ⚠️ FILTER queryTypes OR YOUR ANSWER IS NOISE: too_broad and long_tail are category demand and dominate any total, so 'my biggest gap' unfiltered returns head terms like 'makeup'. Use ['core','presence','suggested','competitor'] for actionable work, ['core'] for your tight market, ['own_brand'] for brand defence. 🔗 CROSSING WITH PPC: group by keyword and each row carries variants, the spellings that query merges — filter query_advertising/query_search_terms with ALL of them, because 35% of served queries have several spellings and they carry 60% of the volume, so matching one string silently misses real campaigns. The reverse works too: pass your PPC targets into keywords here and they resolve through the same clustering. Metric keys are their OWN universe — not list_metrics keys, not ads keys. 💱 CURRENCY: monetary values are ALWAYS served in the organization's primary currency — the secondary currencies are not supported on this route; currency in the response is the code and currencyNotice, when present, MUST be relayed to the user.

Inputs: grain (required), metrics (required), q, to, +15 more.

query_subscribe_and_saveA
Read-only
Inspect

SUBSCRIBE & SAVE: the programme's health, its offers and each product's state, from Amazon's own Replenishment figures (daily snapshots). Four sections. health (per account × marketplace, as of the latest snapshot): lastMonth (units, revenue, active subscriptions, revenue lost to stockouts, revenue penetration, coupons), retention (subscriptions retained after 30 / 90 days), subscribers (average revenue and reorders of a subscriber vs a non-subscriber, revenue from subscriptions with several deliveries / one delivery still active / one delivery then cancelled), fundingTiers (revenue share and sign-up conversion of the seller-funded discount tiers 0 / 5 / 10 / 5+ %), lifetimeValue (by customer segment, one-time purchases vs subscriptions) — every block carries ITS window: the base figures are last month, the others trailing 12 months (24 for lifetime value), and Amazon gives them per account only, never per ASIN. The health's amounts are in each marketplace's own currency (the row's currency), or in the currency you pass, one of the organization's configured codes: each block is then converted at the average daily rate over its own window, convertedFrom naming the marketplace's currency, and an amount whose window has no rate reads null, never unconverted. Pass the currency query_metrics answers in to read the amounts as the cockpit's Subscribe & Save program card shows them. offers (per ASIN × SKU × marketplace): eligibility (ELIGIBLE | INELIGIBLE | SUSPENDED — INELIGIBLE cancels the subscriptions; SUSPENDED: Amazon has suspended the offer from Subscribe & Save, and its existing subscriptions still count in Amazon's figures; what Amazon does with their deliveries is not established, so state the suspension, never a consequence), subscriptions, inventory and stockRisk, price, the funded discounts (seller and Amazon, base and tiered, in %), autoEnrollment, forecastDeliveries at 15/30/60/90 days (units), deliveries30d by condition with atRisk (Amazon's at-risk count never includes a suspended offer), forecastRevenue at 30/60/90 days. changes: the eligibility transitions of the last sinceDays days: kind = loss when the offer leaves ELIGIBLE (a suspension included, which is not a cancellation), recovery when it returns to ELIGIBLE, other between two states that are not ELIGIBLE. Each change also carries marketplaceCode (the code the seller says, US or DE; marketplace keeps the id) and subscriptionsCancelled, true when the offer turns INELIGIBLE, SUSPENDED → INELIGIBLE included (a kind other). The statuses: ELIGIBLE serves the current subscriptions and takes new ones; SUSPENDED: no new subscriptions; INELIGIBLE: no new subscriptions, and Amazon cancels the existing ones. The daily check is section changes with sinceDays 1, keeping the rows where subscriptionsCancelled is true or eligibility is SUSPENDED with previousSubscriptions > 0; the answer's snapshots gives each account's latest offer snapshot (null: no offer snapshot in this scope), and its notice, when present, names the accounts whose snapshot of the day (UTC) has not landed yet: an empty list for them means not read yet, never no change, so relay it. summary (one row per product as of the latest snapshot of each account and marketplace: the cockpit's S&S Health column): per ASIN, or per ASIN × SKU with groupBy='sku'; one row over all the product's marketplaces, or one per marketplace with byMarketplace=true (marketplace then names it). A row adds up the accounts of the call that carry the product: pass accounts to read one. Each row carries subscriptions (its active subscriptions; null when Amazon reported none of its offers' counts), forecastDeliveries30d (the units Amazon plans to deliver to subscribers over the next 30 days), deliveries30d by Amazon's condition: pausedNonBuyable and pausedPricing (PAUSED: those deliveries are stopped, the offer not buyable or for a pricing issue), lowInventoryRisk (AT RISK: still scheduled, threatened by low inventory) and noIssues; suspendedOffers and suspendedSubscriptions (SUSPENDED as in offers: their subscriptions count in subscriptions and in the forecast, and Amazon's at-risk count never includes them), and suspendedOffersWithSubscribers, the suspended offers that carry subscriptions; ineligibleOffers (the INELIGIBLE ones only, their subscriptions cancelled); eligibility, Amazon's status over the product's offers, the one rule of every Subscribe & Save surface: SUSPENDED when a suspended offer carries subscriptions (SUSPENDED as in offers: state the suspension, never a consequence), else ELIGIBLE when one offer is ELIGIBLE or REPLENISHMENT_ONLY_ORDERING, else SUSPENDED when one offer is, else INELIGIBLE when every offer is, else null; a suspended offer without subscribers on an otherwise eligible product leaves it ELIGIBLE (mention it, e.g. '1 suspended offer, no subscribers', never as the product's state); sellerFundedBaseDiscountPct { min, max }, the base discount the seller funds on the product's offers in % (min and max equal on a single offer; null when Amazon reported none); offers, marketplaces and snapshotDate; and health, the worst of Amazon's warnings: paused_non_buyable, then paused_pricing, at_risk_low_inventory, suspended (a suspended offer with subscribers), else no_issues. The products Amazon warns about come first, then the most subscribed, so limit cuts quiet products first. Counts and units only, no amount. For the S&S sales, units, active subscriptions, stockout loss (in sales and in units) and the discount the seller funded OVER A PERIOD and by product, use query_metrics (activeSubscriptions, shippedSubscriptionUnits, totalSubscriptionsRevenue, salesPenetration, lostSubscriptionsRevenue, subscriptionsStockoutRate, missedSubscriptionUnits, subscribeAndSaveDiscount), whose answer says when the S&S figures of a period are partial or incomplete; for the projected units next to days of inventory, query_inventory.

Inputs: section (required), skus, asins, limit, +7 more.

set_stock_defaultsA
Destructive
Inspect

Set ONE account's numbers of the TOP table of the Supply chain page — the warehouse & 3PL setup: per warehouse (its stock region, or its name as get_setup domain=supply_chain lists it) the transit to Amazon, the target stock at Amazon, the target stock at the warehouse and the transit from the factory; per account (region 'ALL') the production lead time; and the factory lines (goods straight from a country to a territory). These are ranks 3 and 4 of the ladder, above the fleet default (rank 5, Nova's number, the page's gold figure) and below the product's own lines (import_supply_chain): a value set here reaches every product without its own number. Fields you omit keep their current value, null clears one; when a line's numbers end up blank its row is deleted. Give ONE region at the top level (the form of before 2026-10-22), or rows (several regions or warehouses at once) and / or factoryLines. TWO-STEP: call WITHOUT commit to preview current → new per parameter, show the user, then commit with the confirmationToken. Requires the OAuth connection and the OWNER role.

Inputs: account (required), rows, commit, reason, +8 more.

set_tacos_default_targetA
Destructive
Inspect

Set the organization's DEFAULT TACOS target: the target every product without its own is held against (12 % until the organization sets one). A WHOLE percent from 0 to 100 (12 = 12 %, never 0.12; 0 = no ads wanted by default). Changing it touches no product's own target (import_tacos_targets sets those, and a null target there sends a product back to this default). TWO-STEP: call WITHOUT commit to preview current → new, show the user, then commit with the confirmationToken. A committed change is announced to the Nova team, with your reason: say why. One workspace in scope = implicit; several = pass workspace. Requires the OAuth connection and the OWNER role.

Inputs: target (required), commit, reason, workspace, +1 more.

set_vat_default_categoryA
Destructive
Inspect

Set (or clear) ONE account's DEFAULT VAT category — the category every product without its own falls back to. 'A_NOVA_ZERO' is the zero-rated switch (VAT handled outside Nova, or VAT-free sales); a real code (e.g. 'A_GEN_STANDARD') applies one category to the whole catalog. TWO-STEP: call WITHOUT commit to preview current → new, show the user, then commit with the confirmationToken. category null clears the default. Requires the OAuth connection and the OWNER role.

Inputs: account (required), category (required), commit, reason, +1 more.

update_listing_contentA
Destructive
Inspect

Seller Central only (a Vendor Central account is refused by name: its content is changed in Vendor Central). Change listing CONTENT on Amazon (title, bullets, description, backend keywords, dimensions, any editable product-type attribute — never the offer: price, stock, shipping, tax, condition or offer images, which Nova refuses as not-editable) for up to 50 SKUs of ONE account on ONE marketplace. Each row is { sku, attributes: { column: value } } with the columns get_listing_content returns: a string for a text attribute, an array of strings for bullet_point, a number for a numeric leaf, null to DELETE an attribute; a column you omit is untouched. TWO-STEP, never skip the preview: call WITHOUT commit; the server diffs against Amazon's current values, validates locally against the product type schema and on Amazon (VALIDATION_PREVIEW — nothing is written), and returns the before → after table, the issues and a confirmationToken; show them to the user and only after explicit approval call again with the SAME account/marketplace/rows plus commit:true and the token. ACCEPTED means Amazon took the change for processing; STORED (about two minutes later) means Amazon holds it; PUBLISHED means the public product page shows it, verified on the public catalogue within minutes to hours and re-checked for 72 hours. get_listing_change_status gives each status with its clocks and the next check. For more than 50 SKUs, point the user to the bulk template in Nova. Requires the OAuth connection, the OWNER role, and the Amazon write flag on the workspace.

Inputs: rows (required), account (required), marketplace (required), commit, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted analytics for a single Amazon seller account, pulling Seller Central and Advertising data into Postgres and serving it to Claude via a bearer-token-guarded HTTP endpoint.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects Amazon Seller Central and Amazon Advertising to any MCP client, with a settlement-accurate P&L underneath: every fee, refund and reimbursement as Amazon actually posted it, so contribution margin and breakeven are per product, per marketplace, per day. 107 tools spanning P&L, full Sponsored Products/Brands/Display management, Search Query Performance and Brand Analytics, inventory and for
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables sellers to interact with Amazon Selling Partner API and Advertising API data—orders, inventory, pricing, ads, reports, and more—through MCP clients like Claude and Cursor.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.