Easyparser — Amazon Product & Seller Data

get_seller_profile

Read-only

Unmask the legal identity and reputation of any Amazon merchant: legal business name, registered business address, and granular feedback trends over 30/90/365 days and lifetime. This is the supplier-verification and brand-protection tool.

Use this tool when the user asks 'who is this seller?', 'is this merchant legitimate?', or needs a supplier's legal entity for compliance or invoicing. To see WHAT the seller sells, use get_seller_products. To read individual buyer reviews about the seller, use get_seller_feedback.

Provide EITHER seller_id OR url — never both. You can discover a product's seller by calling get_product_offers first. Costs 1 credit.

Input Schema

Name	Required	Description	Default
`url`	No	Full Amazon seller profile or storefront URL (e.g. https://www.amazon.com/sp?seller=A1MCYUGJD2ILFU).
`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
`language`	No	Language code for the Amazon page, in locale format (e.g. en_US, de_DE, tr_TR). Affects the language of titles, descriptions and reviews in the response.
`seller_id`	No	Amazon's unique seller identifier (e.g. A1MCYUGJD2ILFU). Found in seller profile URLs as the 'seller=' or 'me=' parameter.

Output 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

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely non-inferable behavior: a 1-credit cost, and the constraint that it unmask a legal entity (emphasis on data sensitivity/privacy). It stops short of noting rate limits or what happens when a seller_id is invalid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the capability, then triggers, then sibling routing, then the parameter constraint and cost. Every sentence carries distinct information; nothing is restated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value detail is unnecessary, and the description instead covers the things an agent actually needs to decide and invoke: when to choose it, what it returns at a high level, acceptable inputs, discovery path, and cost.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description exceeds that by adding the mutual-exclusion rule 'Provide EITHER seller_id OR url — never both', which the JSON schema does not encode (no oneOf/anyOf), plus the hint that seller_id can be discovered from get_product_offers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Unmask the legal identity and reputation of any Amazon merchant') and enumerates the exact payload: legal business name, registered address, and 30/90/365-day plus lifetime feedback trends. It self-labels as 'the supplier-verification and brand-protection tool', which instantly separates it from the product- and review-oriented siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives literal trigger phrasings ('who is this seller?', 'is this merchant legitimate?'), states the compliance/invoicing context, and explicitly routes elsewhere for adjacent needs ('To see WHAT the seller sells, use get_seller_products. To read individual buyer reviews... use get_seller_feedback'). It even documents the discovery path via get_product_offers.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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.