Apiguru Amazon Data

Seller profiles for up to 10 seller IDs

seller_profile_batch

Read-onlyIdempotent

Returns the storefront profile for each seller id: business name, rating, feedback counts, address and marketplace presence. Price: $0.012 per item (max 10). Seller ID validation is all-or-nothing: one malformed id rejects the entire request with 400. Every row in results is an object with status: ok (the profile), not_found (Amazon has no page for that id on this marketplace; billed, like a 404) or unavailable (Amazon served nothing usable on any route; NOT billed on the keyed path, retryable: true). A row is never null. billable_requests_count counts ok + not_found rows; on the pay-per-call rail the per-item quote is settled up front, so retry unavailable ids in a separate call rather than expecting a partial refund.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`geo`	No	Marketplace country code.	US
`seller_ids`	Yes	Comma-separated seller IDs, maximum 10. Each must be 13-15 alphanumeric characters or the whole call 400s.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`results`	No
`request_id`	No
`unavailable`	No
`country_code`	No
`response_time`	No
`amazon_request_count`	No
`billable_requests_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 21, 2026

addedOutput schema / properties / note

Added value: +{
+  "default": null,
+  "title": "Note"
+}

addedOutput schema / properties / unavailable

Added value: +{
+  "default": null,
+  "title": "Unavailable"
+}

Changed1 schema field changedSep 6, 2026
- addedInput schema / properties / seller_ids / pattern
```
Added value: +"^[A-Za-z0-9]{13,15}(,[A-Za-z0-9]{13,15})*$"
```
First observedSep 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes far beyond annotations: it discloses all-or-nothing validation, billing rules for each status, that rows are never null, the billable_requests_count semantics, and the pay-per-call settlement. It also explains the 'unavailable' status is not billed and is retryable. This is comprehensive behavioral disclosure that annotations alone do not provide.

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?

The description is dense but every sentence adds value: return contents, pricing, validation rule, status semantics, billing count, and retry advice. It is front-loaded with the core purpose and then details edge cases. No wasted words or redundancy.

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 format is covered. The description thoroughly addresses edge cases (malformed IDs, not_found, unavailable), billing behavior, retry strategy, and the max limit. For a batch tool with nuanced error handling, this is complete and actionable.

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

Parameters3/5

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

Schema description coverage is 100%, with both parameters already well-documented in the schema (geo enum with default, seller_ids pattern and max 10). The description adds minor context about validation and pricing, but the schema already carries the semantic weight. Baseline 3 is appropriate given high schema coverage.

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 clearly states the tool returns storefront profiles for seller IDs, listing specific data fields (business name, rating, feedback counts, address, marketplace presence). The verb 'returns' and resource 'storefront profile' are unambiguous, and the batch nature distinguishes it from singular profile tools among siblings like seller_products or seller_reviews.

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

Usage Guidelines4/5

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

The description provides explicit usage guidance on handling different statuses (ok, not_found, unavailable), billing implications, and a direct instruction to retry unavailable IDs in a separate call. However, it does not explicitly compare against alternative tools or state when to prefer this over siblings, so a slight gap remains.

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

All Apiguru Amazon 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.