Create a campaign DRAFT for the authenticated tenant. A draft persists the campaign structure (name, subject, content, audience) but does NOT schedule or send it. Use when the user wants to compose a new email campaign without sending it yet. Do NOT use to schedule or send — scheduling/sending a campaign is done with mcp_crm_campaigns_send; this tool deliberately rejects scheduleTime and any send-status argument. Supply an idempotencyKey to make a retried create safe (the same key + same payload returns the original draft instead of creating a duplicate). Returns the created draft projection plus an opaque version token for a later update. SENDER: omit senderEmail/fromId to default to the authenticated MCP user's own verified sender identity. If that user is not in the account's verified sender list the call is rejected with 'sender_selection_required' and the response lists the available verified senders, so the user can choose one and the call can be repeated with senderEmail (or fromId) set to it. A senderEmail/fromId that is not a verified sender is rejected with 'sender_not_verified'; an account with no verified sender at all is rejected with 'no_verified_sender'. Omit replyToEmail and replies go back to that same sender address. The campaigner/owner of the draft is always the authenticated MCP user and cannot be set via a tool argument. TYPE: pass type ONLY when the user says which kind of campaign they want (Regular or ABTesting); omit it and the draft is created as Regular. Regular is the default for an ordinary campaign. AUDIENCE: campaignSegments takes raw segmentTypeId + segmentIds. When the user has not given exact ids, they come from mcp_crm_audience_select, which lists groups, segments and tags with each one's contact count, reports the de-duplicated recipient total, checks it against the account's daily and monthly email limits, and returns a campaignSegments block that can be passed here unchanged. CONTENT / TEMPLATES: the account's saved email templates are listed by mcp_crm_templates_list (searchable by name) and read by mcp_crm_templates_get; a template's content can be the starting point for the campaign. Templates do not store a subject line, so the campaign subject is set here. When the content comes from a template, passing that template's contentJson and editorType keeps the campaign in the same editor as the template. editorType otherwise defaults to the HTML editor for plain HTML, and to the Unlayer design editor (1) whenever contentJson is passed. IMAGES: image URLs in the content should come from mcp_crm_assets_image_import (a public https image URL) or mcp_crm_assets_image_upload (image bytes the user supplied). Any external image left in the content is re-hosted on the account's CDN automatically, but an image that cannot be fetched keeps its original URL and may not render for recipients. SENDING DOMAIN: campaignData.domainName sets which of the account's sending domains the campaign goes out on. If it is omitted, the account's first sending domain is used and returned as domainName in the response. A domainName that is not one of the account's sending domains is rejected with 'domain_not_available' and the response lists the available domains. Tenant is bound to the session and cannot be set via tool arguments.