Related Servers

Many tools have overlapping boundaries: update_page_element vs update_page_elements vs update_page_source, invoke_tool vs invoke_read_tool (which shadow every other tool), and the parallel 'global source' (cart/popup) versus 'global section' (header/footer) families with near-identical verb sets (list/get/search/update/delete) are easy to confuse. Page creation is split across create_page, build_page, start_page_draft + add_draft_section + commit_page_draft, and new_page_skeleton, so an agent must reason carefully to pick the right path.

The overwhelming majority of names follow consistent snake_case verb_noun (list_products, get_product, create_article, delete_collection). Deviations are minor and readable: new_element/new_section/new_row break the verb pattern slightly, get_source_cart is noun-order odd, and edit_http_function vs update_http_function use different verbs for related operations.

132 native tools is a gross mismatch for any single server surface; the presence of a tool-group/search_tools/on-demand catalog mechanism is itself an admission that the native set is oversized. The many one-off helpers (toggle_debug_render, restore_file_version, read_cached_result, list_cached_results, semantic_search_themes) inflate the count further than the domain requires.

Coverage of the storefront-builder domain is very broad: pages, elements, sections, drafts, publishing, products/categories, articles/blog categories, orders, customers, promotions, collections, CMS/HTTP functions, apps, themes, images, and version rollback all have lifecycle tools. Remaining gaps (shipping, domains/SEO beyond page-level SEO, marketing/CRM, translations for products) exist but are largely reachable via search_tools/invoke_tool, so agents have workarounds.