OpenPhone MCP by usefulapi

Each tool maps to a distinct resource plus action: call-related tools (get_call, get_call_recordings, get_call_summary, get_call_transcript) return clearly different artifacts, and list vs get variants (get_message vs list_messages) are unambiguous. No two tools appear to do the same thing.

Nearly all tools follow a clean openphone_verb_noun pattern (create_contact, get_call, list_calls, send_message). The only deviation is openphone_get_contact_custom_fields, which is a listing operation but uses the 'get' verb and adds a longer noun phrase.

16 tools is reasonable for a communications API spanning calls, messages, contacts, conversations, numbers, users, and webhooks, and each tool earns its place. It sits just over the typical 3-15 sweet spot, but no tool feels redundant.

Contacts only support create/get/list with no update or delete, and conversations, phone numbers, users, and webhooks are strictly read-only (webhooks cannot be created or deleted at all). The read surface is broad and coherent, but notable write/mutation gaps limit full lifecycle coverage.