Upload Contact List CSV and Create Contact List Audience
upload_contact_list_csv_audienceCreate a contact-list audience from either inline contacts over the authenticated MCP connection or a private, expiring CSV URL. Exactly one source is required. Signed URLs must use S3/GCS signatures or an Azure read-only HTTPS SAS, expire within one hour of issue, and refer to an object inaccessible without its signature. Public URLs and redirects are rejected.
The CSV header is exactly email,firstname,lastname,jobtitle,employeecompany,country,appleidfa,googleaid (case-insensitive and whitespace-trimmed). Email is required; other columns can be blank. Accepts 300 to 300,000 contacts. The server validates the file and uploads it through the platform's upload flow. Returns the audience creation result and ID or validation errors. Audience readiness and channel matching occur asynchronously.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"audience_name": "<audience_name>"
},
"name": "upload_contact_list_csv_audience"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| contacts | No | Inline array of contact objects (optional). Each object represents one person/contact with fields: email (required), firstname, lastname, jobtitle, employeecompany, country, appleidfa, googleaid. Minimum 300 contacts, maximum 300,000 contacts. MUTUALLY EXCLUSIVE with `contacts_source_csv_url` — provide exactly one. | |
| audience_name | Yes | Name for the new contact list audience (required). | |
| contacts_source_csv_url | No | Private S3/GCS signed HTTPS URL or Azure read-only SAS valid for at most one hour. The object must not allow anonymous access. Public URLs and redirects are rejected. Mutually exclusive with inline contacts. |