No user-submitted related servers found.
Scored across 185 tools
The set contains many near-overlapping tools despite detailed descriptions: publish tools such as post_to_x vs post_x_article and post_to_linkedin vs post_to_linkedin_page, plus a large creation cluster (generate_video, render_ad, make_explainer, product_sizzle, stitch_video) and editing cluster (edit_video, restyle_video, recast_motion, multiply_ad, hook_variants, fix_beat). Aliases like clone_static/remix_static and generic access paths like store_get vs the typed getters add avoidable ambiguity. Descriptions help, but at 185 tools many boundaries are still easy to misselect.
Names are overwhelmingly snake_case, so the mechanical convention is stable. However verb patterns are mixed across large families: post_to_, generate_, make_, render_, plan_, create_, list_, get_, update_, delete_, and noun-first/status names such as error_detail, billing_status, hook_variants, and hermoso_capabilities. It remains readable, but not a predictable verb_noun set.
185 tools is an extreme mismatch for a coherent tool set and far beyond the 30-50 tool range where selection quality tends to hold up. The enable_tools/find_tools/call_tool routing is a thoughtful mitigation, but it does not change the fact that the surface itself is enormous. This is the dominant coherence problem.
The surface is extraordinarily broad, covering brand setup, research, image/video generation, publishing, scheduling, analytics, billing, files, connectors, memory, skills, playbooks, and creator/lead workflows. Minor gaps remain, such as direct published-post management/deletion tools referenced in descriptions but not present in the listed surface. Overall it is close to complete for a marketing/ads automation domain.
