No user-submitted related servers found.
Scored across 59 tools
Most tools target a clearly distinct resource and action, with explicit guidance separating campaigns from transactional messages and templates from gallery designs. A few pairs like get-email vs get-email-campaign and list-emails vs list-email-campaigns could be confused, but the descriptions resolve them well.
Tool names follow a highly predictable kebab-case verb_noun pattern throughout, e.g. list-contacts, create-email-campaign, add-contacts-to-list, clone-in-app-campaign. Minor singular/plural differences such as get-email vs list-emails are still readable and consistent with the overall convention.
With 59 tools, the surface is very large even for a multi-channel marketing platform, and the repeated CRUD patterns across contacts, lists, tags, campaigns, templates, properties, events, and transactional messages create significant cognitive load. Many operations could likely be grouped or parameterized by channel/resource rather than exposed as separate tools.
The server covers create/read/update for core resources, but there are notable lifecycle gaps: no delete operations for contacts, lists, tags, campaigns, templates, properties, or events, and sending/scheduling campaigns is explicitly left to the dashboard. Transactional messages support only list/get, which limits the surface for testing or inspecting sends.