linkfox-amazon-store-customer-feedback

Original：🇺🇸 English

Translated

10 scriptsChecked / no sensitive code detected

亚马逊店铺买家反馈洞察（与 linkfox-amazon-store-auth 等同系列），经 /spApi/developerProxy 调用 SP-API Customer Feedback v2024-06-01：getItemReviewTopics、getItemBrowseNode、getBrowseNodeReviewTopics、getItemReviewTrends、getBrowseNodeReviewTrends、getBrowseNodeReturnTopics、getBrowseNodeReturnTrends。当用户提到评论主题、评价趋势、退货主题、browse node 反馈、Customer Feedback API、MENTIONS、STAR_RATING_IMPACT、ASIN 评论洞察、类目节点评价时触发。

23installs

Sourcelinkfox-ai/linkfox-skills

Added on2026-07-04

NPX Install

npx skill4agent add linkfox-ai/linkfox-skills linkfox-amazon-store-customer-feedback

SKILL.md Content

View Translation Comparison →

Amazon 店铺 Customer Feedback

本 skill 与 linkfox-amazon-store-auth
等同属 Amazon Store 系列：先 POST /spApi/storeTokens
，再 POST /spApi/developerProxy
转发 GET。

说明：接口属于 Customer Feedback（买家评论/退货洞察），不是 Orders 订单 API。订单见 linkfox-amazon-store-orders
。

官方参考索引

能力	文档
getItemReviewTopics	getItemReviewTopics
getItemBrowseNode	getItemBrowseNode
getBrowseNodeReviewTopics	getBrowseNodeReviewTopics
getItemReviewTrends	getItemReviewTrends
getBrowseNodeReviewTrends	getBrowseNodeReviewTrends
getBrowseNodeReturnTopics	getBrowseNodeReturnTopics
getBrowseNodeReturnTrends	getBrowseNodeReturnTrends

Prerequisites

依赖 linkfox-amazon-store-auth
。
通常需 Brand Analytics 或 Selling Partner Insights 等角色；站点以官方为准（常见 US/UK/DE 等）。
ASIN 一般为子体 ASIN；topics 类接口需 sortBy
：
```
MENTIONS
```
或
```
STAR_RATING_IMPACT
```
（常各调一次对比）。

Current Capabilities

脚本	path 要点
`get_item_review_topics.py`	`.../items/{asin}/reviews/topics`
`get_item_browse_node.py`	`.../items/{asin}/browseNode`
`get_item_review_trends.py`	`.../items/{asin}/reviews/trends`
`get_browse_node_review_topics.py`	`.../browseNodes/{browseNodeId}/reviews/topics`
`get_browse_node_review_trends.py`	`.../browseNodes/{browseNodeId}/reviews/trends`
`get_browse_node_return_topics.py`	`.../browseNodes/{browseNodeId}/returns/topics`
`get_browse_node_return_trends.py`	`.../browseNodes/{browseNodeId}/returns/trends`

前缀均为 customerFeedback/2024-06-01/
。共享模块：_spapi_customer_feedback_common.py
。

Quick Parameters

公共：

sellerId

、

region

、

marketplaceId

（或

marketplaceIds

取首项）。

ASIN 类：
```
asin
```
；topics 类另需 sortBy
。
Browse node 类：
```
browseNodeId
```
（可先
```
get_item_browse_node
```
取得）。

Scripts

bash

export LINKFOXAGENT_API_KEY="<your-key>"

python scripts/get_item_review_topics.py '{"sellerId":"A1...","region":"NA","asin":"B0...","marketplaceId":"ATVPDKIKX0DER","sortBy":"MENTIONS"}'

python scripts/get_item_browse_node.py '{"sellerId":"A1...","region":"NA","asin":"B0...","marketplaceId":"ATVPDKIKX0DER"}'

python scripts/get_browse_node_review_topics.py '{"sellerId":"A1...","region":"NA","browseNodeId":"123456","marketplaceId":"ATVPDKIKX0DER","sortBy":"STAR_RATING_IMPACT"}'

Display Rules

先看 developerProxy.errcode
/
httpStatus
，再读各脚本解析字段（如 itemReviewTopics
）。
网关白名单需包含 customerFeedback/2024-06-01/
。
数据刷新频率以 Amazon 为准（通常按周）。

Feedback：

skillName

：

linkfox-amazon-store-customer-feedback

。

更多跨境 skill：LinkFox Skills

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/check_auth_dependency.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"

Pick
--out-dir
outside any git working tree (e.g.
/tmp/...
on Unix,
%TEMP%/...
on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

This skill exposes multiple entry scripts:

check_auth_dependency.py

,

get_browse_node_return_topics.py

,

get_browse_node_return_trends.py

,

get_browse_node_review_topics.py

,

get_browse_node_review_trends.py

,

get_item_browse_node.py

,

get_item_review_topics.py

,

get_item_review_trends.py

. Pass

--script scripts/<name>.py

to choose the one you need.

run

writes the full response to a file and emits only a schema preview + file path.

read

projects specific fields, with

--limit/--offset

for slicing and

--format json|jsonl|csv|table

for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

High field count per record, or fields you don't need
Batch/paginated results (multiple items per call)
Long-text fields (descriptions, reviews, HTML, time series)
Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via

read

.