sent-contactslisted

# Sent Contacts Operate contacts with `contacts.list`, `contacts.get`, `contacts.create_many`, `contacts.delete`, and `contacts.message_summary`. ## Establish connection and scope Use client-managed OAuth 2.1/PKCE. Never request or expose a token, API key, authorization header, client ID, or secret. Before a mutation, surface the active organization and Sender Profile from the connection context; if either is unavailable, use `sent-account-readiness` to inspect the authorized scope. Reauthorize in the client to change scope. Mask phone numbers where practical. Return only the contact fields needed for the task, and do not repeat contact data after it has been reviewed. Number presence or messaging history does not establish consent. ## Read contacts - Use `contacts.list` to search or page through contacts. Apply the narrowest available filter and do not dump an entire contact book unnecessarily. - Use `contacts.get` when an exact contact identifier is known or before a delete. - Use `contacts.message_summary` for the contact's messaging summary. Distinguish summary data from proof of consent or current reachability. Read-only calls do not require mutation confirmation. ## Create contacts in bulk 1. Validate and deduplicate the proposed records locally. Preserve only fields the user actually supplied. 2. Build the exact `contacts.create_many` arguments without calling the tool. 3. Show a payload preview with the selected organization, Sender Profile, record count, dup