Query keyword rank trends
query_keyword_rank_trendsOne trackingScope per request: PARENT (default) uses parentAsin and tracks the family; CHILD uses asin and tracks only that exact variation, excluding siblings. The server resolves its parent. For tracker lists use parentAsins with PARENT or asins with CHILD. Query, ADD, RESUME, REMOVE and SET_COMPETITORS must preserve the same scope and target. Both OWN_PRODUCT and independent COMPETITOR support CHILD. For OWN_PRODUCT associations, PARENT competitorAsins are parent/standalone ASINs while CHILD competitorAsins are exact variation ASINs. includeCompetitors compares the same scope. Account capabilities and notices are returned even for empty results. Check advertisingRankTracking before interpreting advertising ranks or offering advertising tracking. False means unsupported, not a missing match; never promise advertising ranks or silently substitute organic tracking for an explicit advertising-rank request. This applies to own products, independent competitors, and associated competitors. First discover tracked products and keywords with query_keyword_rank_trackers (all matching configuration is returned without pagination). For DAILY, provide one storeId, one scope-specific ASIN and 1 to 10 exact tracked keywords, plus startDate/endDate (up to 90 inclusive marketplace-local days). All requested daily points return in one response; there is no offset/limit pagination. Split more than 10 keywords into separate requests. Each day keeps the last actual observation; absent days are not synthesized. Equal-time ties use child ASIN descending, current source first, then ID descending, not best rank. RAW uses the same storeId and scope-specific ASIN with exactly one keyword, supports 31 inclusive days, and uses offset and limit (default and maximum 100) over observation points; increase offset by limit until fewer than limit points are returned. RAW preserves distinct child ASINs and prefers current records over archived copies. One product type per request: OWN_PRODUCT (default) or independent COMPETITOR. Call separately for each type; ALL and mixed selections are not supported. Competitors share account-wide marketplace/keyword quota with owned products. MCP reporting and workflow metric date ranges use yyyy-MM-dd and include both startDate and endDate, with at most 95 calendar days per range. For longer read-only reports, split into non-overlapping windows: endDate = startDate plus 94 days, capped at the requested end date; the next startDate is the previous endDate plus 1 day. Apply the same limit independently to comparison ranges. Do not average ratios such as ACOS or ROAS across windows; recompute them from summed base metrics. Do not automatically split advertising write plans or metric-based selectors; obtain a supported analysis window from the user. Keyword ranking trends have separate limits: DAILY supports up to 90 inclusive days and RAW up to 31 inclusive days. For keyword ranking trends, use these interval-specific limits when splitting read-only reports. This reporting limit does not apply to campaign scheduling dates.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| asin | No | Required exact child ASIN for CHILD; omit parentAsin. | |
| limit | No | RAW only: maximum observation points per page, default and maximum 100. Does not limit DAILY results. | |
| offset | No | RAW only: zero-based observation offset. DAILY requires 0. | |
| endDate | Yes | Required inclusive end date in yyyy-MM-dd, interpreted in each store's marketplace time zone. | |
| storeId | Yes | One authorized store ID in sellerId:marketplaceId format. | |
| interval | No | Trend resolution. DAILY keeps the final stored observation in each marketplace-local day, up to 90 inclusive days. Ties use child ASIN descending, current source first, then ID descending. RAW reads one product keyword over up to 31 inclusive days, with offset/limit pagination over observation points. Increase offset by limit; stop when fewer than limit points are returned. | DAILY |
| keywords | Yes | Exact tracked keywords for this product: DAILY 1 to 10, RAW exactly one. DAILY returns the full requested history without pagination. | |
| startDate | Yes | Required inclusive start date in yyyy-MM-dd, interpreted in each store's marketplace time zone. | |
| parentAsin | No | The selected product's tracked parent ASIN. | |
| productType | No | One product type per request: OWN_PRODUCT (default) or independent COMPETITOR. Call separately for each type; ALL and mixed selections are not supported. Competitors share account-wide marketplace/keyword quota with owned products. | OWN_PRODUCT |
| trackingScope | No | PARENT (default) tracks a parent family using parentAsin. CHILD tracks only the specified variation using asin; omit parentAsin. Never silently substitute a parent or sibling. Applies to OWN_PRODUCT and independent COMPETITOR. SET_COMPETITORS supports both scopes for OWN_PRODUCT: parent/standalone competitors for PARENT, exact child competitors for CHILD. | PARENT |
| includeCompetitors | No | Include currently associated competitors' stored histories for the same keyword and trackingScope. OWN_PRODUCT + DAILY only, exactly one keyword, at most 31 inclusive days and 10 associated competitors. PARENT compares parent families; CHILD compares exact associated variations. Compare observedAt before comparing ranks; empty points mean no stored history. This is not independent COMPETITOR tracking. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||