No user-submitted related servers found.
Scored across 27 tools
Each tool targets a distinct resource or action: members, audiences, leads, identities, campaigns, webhooks, and messaging. Even overlapping areas like lead search vs. audience leads are clearly differentiated by the scope. The three webhook tools are for different external services, avoiding confusion.
Most tools follow a consistent verb_noun pattern in snake_case (e.g., list_members, get_audience_detail, create_or_update_lead). The only deviation is the three native webhook tools (rb2b_native_webhook, etc.) which lack a verb prefix, but this is a minor inconsistency given their endpoint nature.
With 27 tools, the server is comprehensive and covers multiple domains (audiences, leads, campaigns, messaging, webhooks). While the count is on the higher side, each tool has a clear purpose and the scope justifies the number. It is slightly above ideal but still well-scoped.
The server has significant lifecycle gaps: there is no way to create or delete campaigns, no delete audience or delete lead, and no update audience. The focus is heavily on reading and sending messages, but full CRUD operations are missing for key resources, which will cause agent failures in workflows requiring deletion or creation of campaigns.