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

> The top 10 reasons customers give when returning products in a browse node, each with its share of the category's returns (US, UK, FR, IT, DE, ES, JP only) — use them to set accura

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

te expectations in the listing. One call — this operation takes no sortBy. Call after customerFeedback_getBrowseNodeReviewTrends; then customerFeedback_getBrowseNodeReturnTrends. Amazon SP-API · getBrowseNodeReturnTopics · GET /customerFeedback/2024-06-01/browseNodes/{browseNodeId}/returns/topics

## Call it

MCP tool call:

```json
{
  "name": "customerFeedback_getBrowseNodeReturnTopics",
  "arguments": {
    "store": "myStore-US",
    "browseNodeId": "<browseNodeId>"
  }
}
```

Tool API (early access — contact us):

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

## 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. |
| `browseNodeId` | string | yes | Browse node ID from customerFeedback_getItemBrowseNode. |

## Result

- `data.returnTopics` — the Amazon payload (already compact ~2 KB — there is no slim mode on this operation): {browseNodeId, displayName, marketplaceId, countryCode, dateRange: {startDate, endDate}, topics: [ReturnTopic] (up to 10)}, ReturnTopic = {topic (the return-reason theme), browseNodeMetrics: {occurrencePercentage: {allProducts}} (the share of category returns that cite this reason)}. Return topics carry NO reviewSnippets and NO subtopics — unlike the review-topics operations.