No user-submitted related servers found.
Scored across 207 tools
Descriptions go to extraordinary lengths to state when to use one tool over another (generate_video vs render_ad vs stitch_video, clone_static vs remix_static, the many make_* film tools), which rescues most boundaries. But 207 tools still create real overlap zones—multiple 'make a video/creative' lanes, clone_static explicitly aliased by remix_static, and several save_to_* destination tools that differ only by target. An agent will frequently hesitate between nearby creative and publish tools.
Most names follow snake_case with a verb or channel prefix (post_to_x, generate_image, delete_creator, list_*), giving a readable feel. But the convention is mixed: noun-first names (hermoso_credits, competitor_teardown, product_sizzle, hook_variants), reversed store_get, and verb-first create_brand coexist with no single pattern. Still interpretable, but not a predictable scheme.
207 tools is a severe mismatch for a coherent roster; the server itself concedes this by holding most tools out of the list and shipping find_tools/call_tool/enable_tools to reach them, and documenting that rosters past 30-50 degrade tool choice. The count is extreme by design, not incidental.
The surface is remarkably complete: full CRUD across every channel, every publishing destination, billing, memory, connectors, teams, analytics and a deep creative lifecycle (plan, render, edit, localize, reframe, variants, score). It is over-complete rather than gap-ridden; almost any marketing workflow has a tool for it.
