Amazon Seller MCP Server — AgentXray

One listing's image slots, shown, against the six image roles

get_listing_images

Read-onlyIdempotent

One listing's image slots read LIVE from Amazon (main + 8), with the pictures themselves so you can see them: what buyers are shown per slot, size and zoom, empty slots, images Amazon has flagged, and slots where another contributor's image wins over the seller's. Returns the six roles a complete image stack fills (main image that wins the click, what's in the box, the difference, a five-second infographic, lifestyle in use, the objection handler). Look at the images, say which role each fills and which roles are missing; draft a replacement with draft_image_swap once the seller has the new image. Its narrative is the measured part.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sku": "<sku>"
    },
    "name": "get_listing_images"
  }
}

Input Schema

Name	Required	Description
`sku`	Yes	The seller SKU.
`account`	No	Seller id of the client account (agencies).
`marketplace_id`	No	The marketplace of that listing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the read-only and idempotent annotations, it discloses live Amazon sourcing, the visual payload, and important edge cases such as empty slots, flagged images, and images contributed by another seller winning. It does not clarify how size and zoom are represented, and the closing statement about `narrative` is too cryptic to add much behavioral understanding.

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

Conciseness4/5

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

The live purpose and visual output are front-loaded, and most of the detail supports correct invocation or interpretation. However, the long, densely packed sentences and the meta-sounding phrase "Its `narrative` is the measured part" reduce immediate readability.

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

Completeness4/5

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

Despite having no output schema, it covers the source, nine image slots, returned pictures, notable slot conditions, evaluation framework, and next action. The unexplained `narrative` field and unspecified representation of size and zoom leave minor output-interpretation gaps.

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%, so the schema already documents sku, account, and marketplace_id. The description reinforces that the target is one listing but adds no meaningful parameter formats, selection rules, or interactions beyond those structured descriptions.

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 precisely defines a live, per-slot visual audit of one Amazon listing, including the actual pictures, slot states, and contributor-winning images. Its six-role gap analysis distinguishes it from generic listing-issue tools and from the subsequent replacement-drafting workflow.

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 explicitly tells the agent to inspect the images, identify each image's role, and report missing roles. The conditional handoff to draft_image_swap once the seller has a new image clarifies both the intended workflow and when to use the alternative tool.

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

All Amazon Seller MCP Server — AgentXray 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.

Resources

Need Help?