Easyparser — Amazon Product & Seller Data

get_seller_feedback

Read-only

Read individual buyer feedback entries for an Amazon seller: star ratings, comment text, and dates — filterable by rating range and time period. This is the reputation deep-dive tool.

Use this tool when the user wants to read actual buyer comments about a seller, analyze complaint patterns, or audit service quality. For aggregate reputation scores (30/90/365-day percentages) without individual comments, get_seller_profile is sufficient and cheaper in context.

Each page costs 1 credit. To find dissatisfied customers, set max_rating to 3 instead of paging through everything.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	No	Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across marketplaces.	.com
`max_page`	No	Ending page number. Each page costs 1 credit; max 5 pages per request. Default 1.
`min_page`	No	Starting page number. Default 1.
`seller_id`	Yes	Amazon's unique seller identifier (e.g. A1MCYUGJD2ILFU). Found in seller profile URLs as the 'seller=' or 'me=' parameter.
`max_rating`	No	Maximum star rating to include (1-5). Set to 3 to focus on negative feedback. Default 5.
`min_rating`	No	Minimum star rating to include (1-5). Default 1.
`history_range`	No	Time period filter: '1' or '3' or '12' for months, 'all' for everything. Default 'all'.	all

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Parsed Amazon data for the operation.
`success`	Yes	True when the request completed.
`operation`	Yes	Easyparser operation that ran, e.g. DETAIL or OFFER.
`request_id`	No	Easyparser request ID, useful for support and error logs.
`credits_used`	No	Credits charged for this request.
`credits_remaining`	No	Credits left on the account after this request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "credits_remaining": {
+      "description": "Credits left on the account after this request.",
+      "type": "number"
+    },
+    "credits_used": {
+      "description": "Credits charged for this request.",
+      "type": "number"
+    },
+    "data": {
+      "description": "Parsed Amazon data for the operation."
+    },
+    "operation": {
+      "description": "Easyparser operation that ran, e.g. DETAIL or OFFER.",
+      "type": "string"
+    },
+    "request_id": {
+      "description": "Easyparser request ID, useful for support and error logs.",
+      "type": "string"
+    },
+    "success": {
+      "description": "True when the request completed.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "operation"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

Score is being calculated.

All Easyparser — Amazon Product & Seller Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.