Skip to main content
Glama

Amazon seller products

run_amazon_seller_products
Read-onlyIdempotent

List products sold by an Amazon seller's storefront: title, URL, price, rating, and image. 1 point per returned record.

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": {
      "seller": "<seller>"
    },
    "name": "run_amazon_seller_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoDomain. Options: amazon.com = amazon.com, amazon.co.uk = amazon.co.uk, amazon.de = amazon.de, amazon.fr = amazon.fr, amazon.it = amazon.it, amazon.es = amazon.es, amazon.ca = amazon.ca, amazon.co.jp = amazon.co.jp, amazon.com.mx = amazon.com.mx, amazon.com.br = amazon.com.br, amazon.in = amazon.in, amazon.com.au = amazon.com.au, amazon.nl = amazon.nl, amazon.se = amazon.se, amazon.pl = amazon.pl, amazon.com.tr = amazon.com.tr, amazon.ae = amazon.ae, amazon.sa = amazon.sa, amazon.sg = amazon.sg Default: amazon.com.
sellerYesSeller ID. e.g. A2L77EE7U53NWQ
max_itemsNoMax items (up to 250) Default: 10.
start_pageNoStarting page Default: 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Amazon marketplace domain. Defaults to amazon.com."New value: +"Domain. Options: amazon.com = amazon.com, amazon.co.uk = amazon.co.uk, amazon.de = amazon.de, amazon.fr = amazon.fr, amazon.it = amazon.it, amazon.es = amazon.es, amazon.ca = amazon.ca, amazon.co.jp = amazon.co.jp, amazon.com.mx = amazon.com.mx, amazon.com.br = amazon.com.br, amazon.in = amazon.in, amazon.com.au = amazon.com.au, amazon.nl = amazon.nl, amazon.se = amazon.se, amazon.pl = amazon.pl, amazon.com.tr = amazon.com.tr, amazon.ae = amazon.ae, amazon.sa = amazon.sa, amazon.sg = amazon.sg Default: amazon.com."
    • changedInput schema / properties / max_items / description
      Previous value: -"Maximum number of products to return (1-250, default 10). Billed at 1 point per returned record."New value: +"Max items (up to 250) Default: 10."
    • changedInput schema / properties / seller / description
      Previous value: -"Amazon seller ID, e.g. A2L77EE7U53NWQ."New value: +"Seller ID. e.g. A2L77EE7U53NWQ"
    • changedInput schema / properties / start_page / description
      Previous value: -"Result page to start from (default 1)."New value: +"Starting page Default: 1."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint: true). However, the description adds significant behavioral context by listing the exact data fields returned (title, URL, price, rating, and image), which is valuable information absent in the formal schema.

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 extremely concise. It states the primary function and then efficiently lists all the returned data points in a single, impactful sentence.

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?

Given the simplicity of the operation (listing products) and the completeness of the input schema, the description is highly complete. It clearly communicates the required function and the scope of the results.

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 all parameters are thoroughly defined in the structured schema. The description adds no unique meaning or clarification regarding the structure or purpose of the input parameters.

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 uses the specific verb 'List products' and scopes it precisely to 'an Amazon seller's storefront.' This clearly differentiates it from general product search or listing tools like run_amazon_product_search.

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

Usage Guidelines3/5

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

The tool scope is clear (seller products), but the description does not explicitly guide the agent on when to use this function versus related Amazon seller functions. Usage is implied by the focus on the seller storefront.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources