Text-Em-All MCP by usefulapi

Most tools have clearly distinct resource/action targets, and potentially confusable pairs like create_broadcast vs. create_draft_broadcast and get_broadcast vs. get_broadcast_details are explicitly differentiated. The main ambiguity is text_em_all_request, which overlaps with every dedicated read tool as a generic GET escape hatch, though its description frames it as a fallback.

All tools share the text_em_all_ prefix and snake_case, with mostly predictable verb_noun names such as list_broadcasts, get_account, and update_account_user. The only minor deviation is the generic text_em_all_request, which lacks a resource noun.

At 14 tools, the set is well within a reasonable range and each tool appears to earn its place by covering a specific Text-Em-All operation. The mix of read, write, send, and escape-hatch tools is appropriately scoped.

Core workflows are covered: authentication, account lookup, broadcast creation/drafting/listing/details, text number discovery, 1:1 texting, SSO, and account user add/update. However, mutation lifecycle coverage is notably incomplete: there is no broadcast cancel/update/delete, no contact-list create/update/delete, and no account-user list/delete. The read-only request escape hatch mitigates some GET gaps but not mutation gaps.