# Review insights (https://sellersheetai.com/docs/mcp-api/workflows/reviews)

> Learn what buyers praise and complain about — for your ASIN and for your whole category — and ask delivered orders for a review.



<Callout title="In short">
  Your agent reads Amazon's review topics and trends for an ASIN or a category, return reasons for the category, and can write a buyer-insights report. It can also send Amazon's review request to delivered orders.
</Callout>

## In your daily workflow [#in-your-daily-workflow]

<Steps>
  <Step>
    ### What buyers say about your product [#what-buyers-say-about-your-product]

    `customerFeedback_getItemReviewTopics` returns the top positive and negative topics for your ASIN; `customerFeedback_getItemReviewTrends` shows how they move month to month.
  </Step>

  <Step>
    ### What buyers say about the category [#what-buyers-say-about-the-category]

    `customerFeedback_getItemBrowseNode` finds the ASIN's category; `customerFeedback_getBrowseNodeReviewTopics`, `customerFeedback_getBrowseNodeReturnTopics` and their trend twins show what the whole category is praised for and returned for.
  </Step>

  <Step>
    ### A report to work from [#a-report-to-work-from]

    `customerFeedback_insights_report` writes a buyer-insights report to guide your copy and images; `customerFeedback_insights_report_status` tells you when it is ready. The report is paid from [Credits](/help/app/settings/billing) — priced before it runs, refunded if it fails.
  </Step>

  <Step>
    ### Ask for reviews [#ask-for-reviews]

    `solicitations_getSolicitationActionsForOrder` checks whether an order can be asked; `solicitations_createProductReviewAndSellerFeedbackSolicitation` sends Amazon's own review request.
  </Step>
</Steps>

## Try asking [#try-asking]

> "What are the 10 things buyers praise and complain about most on this ASIN?"

> "How have return reasons in this category trended over 6 months?"

> "Send a review request to these delivered orders."

## Step 1, both ways [#step-1-both-ways]

The same tool and the same arguments — through your AI client, or from your own code.

**MCP** — you ask: "What are the top review complaints for B0EXAMPLE1?" Your agent calls `customerFeedback_getItemReviewTopics` and summarises them.

<ToolCall tool="customerFeedback_getItemReviewTopics" args="{ asin: &#x22;B0EXAMPLE1&#x22;, sortBy: &#x22;MENTIONS&#x22; }" />

<Callout type="warn" title="Write access required">
  Sending review requests acts on your seller account, so the store needs write access (see [Stay in control](/docs/mcp-api/control)). Reading topics and trends works with read access.
</Callout>

## Tools on this page [#tools-on-this-page]

Pulled from the catalog at build time, each with its own access label.

<ToolList domains="[&#x22;customer_feedback&#x22;, &#x22;solicitations&#x22;]" />

## FAQ [#faq]

### Can I turn the insights into new copy and images? [#can-i-turn-the-insights-into-new-copy-and-images]

Yes — hand them to [A+ Content](/docs/mcp-api/workflows/aplus) or [AI images](/docs/mcp-api/workflows/images).

### Is there a skill for the report? [#is-there-a-skill-for-the-report]

Yes — see [Install the skills](/docs/start/skills).