mcp-server

Each tool targets a distinct resource and action; ads, marketplaces, feeds, orders, rules, and categories form separate families with clearly differentiated operations. Parallel tools like get_ad_report and get_ad_item_report are explicitly separated as integration-wide vs item-level, so an agent can reliably pick the right one.

The overwhelming majority follow a consistent verb_snake_case pattern, e.g. list_ads, get_marketplace, map_feed_attribute, delete_rule, set_category_mapping. The main deviation is ad_status and marketplace_status, which use a noun_status pattern instead of the get_*_status used by get_feed_status and get_import_status. Aside from those two, the naming is highly predictable.

With 105 tools, this server is far beyond the 50+ threshold the rubric calls an extreme mismatch. The count is inflated by near-duplicate families across ads, marketplaces, orders, and feeds, which expands the surface far past what is defensible for a cohesive tool set.

CRUD/lifecycle coverage is broad and thorough: feeds support create/get/update/delete/restore/export/submit; marketplaces and ads have full setup, configuration, status, reporting, item actions, and operations; rules, category mapping, order sync, and enrichment sources are all represented. Minor gaps exist (e.g., no delete operation for standalone order connections), but agents can work around them with disable or configure.