Related Servers

Most tools target distinct entities (products, sellers, influencers, deals, promo codes), but there is notable overlap risk: products_by_category and product_search both return products with offers and support the same filters; product_details and product_offers return largely the same product data (with product_offers just adding an offers array); and product_review_details vs product_reviews could be confused (one is a single review by id, the other paginates reviews, though they distinctively differ). These overlaps create selection ambiguity for agents.

The naming pattern is predominantly consistent noun_by_noun / noun_noun (e.g., product_details, product_search, product_reviews, seller_profile, seller_products, influencer_posts, deals). Most tools follow a predictable noun_[verb/noun] style. Minor deviations like asin_to_gtin (verb-based) and product_category_list break the pattern slightly, but overall the convention is coherent.

18 tools is reasonable for a broad Amazon data provider covering products, reviews, sellers, influencers, deals, and promotions. While on the higher end, each tool maps to a distinct Amazon scraping surface area, and the count is justified by the breadth of the domain.

The surface covers a wide variety of Amazon data: product search/details/offers, reviews, sellers, influencers, deals, promo codes, categories, and ASIN conversion. However, there are notable gaps: no update/create/delete operations are expected for a read-only API, but missing tools like cart/order operations and wishlist are acceptable. Gaps like product attributes/browse nodes or warehouse/deep-link retrieval are absent, and it lacks a tool to fetch a single product's reviews for a specific product without cookies (product_reviews requires a logged-in cookie). The truncated descriptions (two tools cut off) make full completeness assessment difficult.