# customerFeedback_getItemReviewTrends (https://sellersheetai.com/docs/mcp-api/tools/customerFeedback_getItemReviewTrends)

> Month-by-month occurrence trends (past 6 months, newest first) of one ASIN's 10 most positive and 10 most negative review topics, beside the category's — to see whether a fix impro

Access: **READ** · toolset amazon_sp · family sp.customerFeedback_2024-06-01

ved sentiment or an issue is growing (US, UK, FR, IT, DE, ES, JP only). Call after customerFeedback_getItemReviewTopics (both sortBy values). Amazon SP-API · getItemReviewTrends · GET /customerFeedback/2024-06-01/items/{asin}/reviews/trends

## Call it

MCP tool call:

```json
{
  "name": "customerFeedback_getItemReviewTrends",
  "arguments": {
    "store": "myStore-US",
    "asin": "<asin>"
  }
}
```

Tool API (early access — contact us):

```bash
curl -X POST https://api.sellersheetai.com/api/v1/tools/customerFeedback_getItemReviewTrends \
  -H "Authorization: Bearer $SELLERSHEET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"store":"myStore-US","asin":"<asin>"}'
```

## Arguments

| Name | Type | Required | Description |
|---|---|---|---|
| `store` | string | yes | the store ref `<store>-<CC>` (name-country, e.g. 'myStore-US') — one of get_user_context's store_refs, verbatim. |
| `asin` | string | yes | the ASIN (e.g. 'B0XXXXXXXX'). |
| `summarize` | boolean |  | true returns the slim shape (~90 % smaller: flat asin_pct and cat_pct lists instead of trendMetrics, no dateRange) — use it in AI workflows; default false returns Amazon's raw payload. |

## Result

- `data.reviewTrends` — the Amazon payload; the topics sit one level down under a second reviewTrends key (data.reviewTrends.reviewTrends) in both shapes.
- `data.reviewTrends.Raw` — {asin, itemName, marketplaceId, countryCode, dateRange: {startDate, endDate}, reviewTrends: {positiveTopics: [TrendTopic], negativeTopics: [TrendTopic]}}, TrendTopic = {topic, trendMetrics: [Period]}, one Period per month, newest first = {dateRange, asinMetrics: {occurrencePercentage}, parentAsinMetrics: {occurrencePercentage} (null with too little data), browseNodeMetrics: {occurrencePercentage: {allProducts}}}. Trends carry occurrence percentages ONLY — numberOfMentions and starRatingImpact are on customerFeedback_getItemReviewTopics. Slim: {positiveTopics: [SlimTrend], negativeTopics: [SlimTrend]}, SlimTrend = {topic, asin_pct: [float] (this ASIN's monthly occurrencePercentage), cat_pct: [float] (the category's monthly allProducts occurrencePercentage)} — parallel, newest first (index = months ago); watch for a rising negative-topic asin_pct against cat_pct.