Skip to main content
Glama

rr_list_products

Read-onlyIdempotent

List inventory items with filters for search, supplier, and review status. Use an exact SKU search with listing identity enabled to resolve Amazon seller SKUs and return ASIN and FNSKU evidence.

Instructions

List inventory items with optional filters. For an exact SKU identity question, provide the exact value in search and set include_listing_identity=true to resolve Amazon seller SKUs and return source listing identifiers such as ASIN and FNSKU.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rr_list_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page (default 100, max 500).
cursorNonext_cursor from the previous page. Pass it with the same other inputs until has_more is false.
offsetNoDeprecated: rows to skip. Use cursor; it stays correct while rows change.
searchNoSearch by name or SKU
vendor_idNoOnly items whose primary supplier is this supplier id (from rr_list_suppliers).
needs_reviewNotrue: only items flagged for review; false: only items not flagged.
include_listing_identityNoSet true only with an exact search value for a SKU identity question. Resolves an exact Amazon seller SKU even when it differs from the canonical SKU and returns listing source, ASIN, and FNSKU evidence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds real value by explaining that identity mode resolves Amazon seller SKUs that differ from the canonical SKU and returns ASIN/FNSKU evidence. It says nothing about default ordering or result volume, but that is a minor gap given annotation coverage.

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?

Two sentences, no filler, with the general behavior front-loaded and the specialized identity mode second. Every clause carries operational meaning.

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?

With seven optional parameters, no output schema, and annotations already covering safety, the description is nearly sufficient. What is missing is a hint about the shape or ordering of returned items, which matters because there is no output schema to fall back on.

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 baseline would be 3; the description goes beyond it by tying two parameters together, requiring an exact search value paired with include_listing_identity=true. That coupling is a semantic constraint not obvious from the individual parameter descriptions.

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

Purpose4/5

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

Opens with a specific verb and resource ('List inventory items with optional filters') and adds a distinct secondary mode for exact SKU identity resolution. It does not explicitly distinguish itself from sibling list tools such as rr_list_slow_movers or rr_list_stockout_risks, so an agent must still infer which listing tool fits a given question.

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?

Gives a clear trigger for the non-obvious path: use include_listing_identity only with an exact search value for an SKU identity question. However, it offers no guidance on when to prefer this tool over alternatives like rr_get_inventory_position for a single item, and no exclusions for the general listing mode.

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