No user-submitted related servers found.
Scored across 31 tools
Tools are largely partitioned by ad product (SP unprefixed, sb_*, sd_*) and by entity type (campaigns, ad groups, ads, targets, negatives), and descriptions explicitly disambiguate near-neighbors like get_creative_asset vs list_creative_assets and get_product_metadata vs creative assets. The main friction is that Sponsored Products tools carry no prefix, so an agent must read descriptions to know get_campaigns means SP while get_sb_campaigns/get_sd_campaigns are separate, and there are many closely-spaced negative target/keyword variants.
All names are snake_case with the amazon_ads_ prefix, which is good, but the verb set is mixed: 'list' is used for profiles and creative assets while 'get' is used for paginated entity listings (get_campaigns, get_sb_keywords), making list vs get semantically overloaded. The ad-product prefixing is also inconsistent, with Sponsored Products tools unprefixed while Brands and Display tools use sb_/sd_ prefixes.
31 tools exceeds the comfortable range and is driven by combinatorial fan-out across three ad products times roughly six entity types, which is defensible for the domain but heavy for an agent to navigate. Much of the surface is repetitive read-one-page variants that could plausibly be consolidated behind a product/entity parameter.
The read surface is thorough across Sponsored Products, Brands and Display entities plus reports and creative/product metadata, but there are no write operations for campaigns, ad groups, keywords, targets, bids or budgets, so the server cannot actually manage or optimize ads. Coverage is a complete read-only lifecycle with no update/delete, which will dead-end agents tasked with making changes.