Tools - Conversion Docs

The MCP server exposes the same catalog of actions Conversion AI uses in chat, with three differences:

It adds raw, immediate edit tools for changing existing assets (see Editing existing assets below).
It adds skill tools so your client can load building references on demand (see Skill tools).
It omits the sandbox and file tools.

For how each tool behaves once your client calls it, and how editing differs from chat, see Differences from chat.

Reading and lookups

Read tools never change anything. They power the “answer questions about my data” side of Conversion AI.

Area	Actions
Contacts	List, get, count, read events and automation runs, list opportunities, list fields, read distinct field values.
Companies	List a company’s opportunities.
Opportunities	List, get, count, list a deal’s contacts. (Opportunities are read-only; they sync in from your CRM.)
Audiences	List.
Emails	List blasts, workflow emails, and templates; get an email; read metrics and recipients.
Forms	List, get, read submissions.
Workflows	List, get, read runs and metrics.
Campaigns	List campaigns, items, members, tokens, token values, types, and type statuses.
Folders	List top-level folders and folder contents.
Workspace	Read email settings and the business logo.
Sync	List sync batches and logs.

Creating new assets

Create tools work the same way over MCP as in chat: a new asset is created live but dormant. Emails, forms, and workflows land as unpublished drafts. Nothing is sent, published, or activated; you still take that step yourself in Conversion.

Area	Actions
Contacts	Create a contact, create a custom field, upload and process a CSV import.
Audiences	Create a static or dynamic audience.
Emails	Create a blast, workflow email, or template.
Forms	Create a form.
Workflows	Create a workflow.
Campaigns	Create a campaign, campaign type, type status, or token. Duplicate a campaign.
Folders	Create a folder, move assets between folders.

Workflows are create-only. There’s no edit flow for an existing workflow. To change one, create a new workflow and switch to it. This matches Conversion AI in chat.

Editing existing assets

To change an asset that already exists, the MCP server exposes raw, immediate-apply edit tools. Each one applies the change to your workspace the moment your client calls it; there’s no preview, no pending list, and no end-of-turn review. This is the biggest behavioral difference from chat; see Editing existing assets for the full comparison.

Tool	What it changes
`update_email`	Update an existing blast or workflow email: name, subject, preview, body, sender, topic, and (for blasts) recipients and scheduled send time. Partial: set only the fields you change. Blasts stay in draft.
`update_form`	Update a form’s metadata: name, CRM-sync, and subscribe behavior.
`update_form_draft`	Replace a form’s design (its draft `FormData`) with a complete definition.
`update_audience`	Update an audience’s name, type, or dynamic filter.
`add_audience_contacts`	Add specific contacts to a static audience.
`update_campaign`	Update a campaign’s or webinar’s name and description.
`campaign_add_members`	Add members: everyone matching a filter for a campaign, or a list of contacts for a webinar.
`campaign_set_token_value`	Set a campaign’s value for one token.
`campaign_update_member_status`	Set a campaign or webinar member’s status. Registered is not available on a webinar.

These tools apply immediately and accept partial updates, so set only the fields you intend to change. Edits to body or design fields (update_email’s data, update_form_draft’s draft) take the complete definition, not a diff, so read the current asset first. The onus is on your client to confirm before calling and to send only what it means to change.

Campaigns and webinars

A webinar is a kind of campaign, and the campaign_* tools cover both. Each one takes a category of either CUSTOM or WEBINAR, because an id on its own doesn’t say which kind it is. A few arguments differ between the two:

campaign_add_members takes a statement filter for CUSTOM and an explicit contactIds list for WEBINAR.
campaign_update_member_status also needs campaignId (the webinar’s id) when the category is WEBINAR, since that endpoint is scoped by webinar rather than by member.
update_campaign’s name sets a webinar’s title. While a webinar is connected to a provider, the provider owns the title and the schedule, so a title edit is rejected until it is disconnected; the description can be set at any time.

A webinar reaches exactly as far as a custom campaign does over MCP: add members, set a member’s status, update the campaign.

Registered is not available over MCP. On a webinar linked to Zoom or a similar host, adding a member at a status of Registered — or moving an existing member to Registered — registers that person with the provider for real, and the provider may email them. Because that reaches someone outside Conversion, campaign_add_members and campaign_update_member_status refuse Registered on a webinar, whether or not that webinar is currently connected to a provider. Registering a member stays a job for a person in the app. Every other webinar status is yours to set; leave statusId unset when adding to use the webinar’s first status (Invited).Connecting a webinar to a provider, disconnecting it, and linking it to Salesforce stay outside the MCP surface entirely: they are actions for a person in the app.

Skill tools

Conversion AI relies on schema references (“skills”) to build emails, forms, workflows, and filters correctly. In chat these load automatically. Over MCP, your client loads them on demand by calling a skill tool before it builds:

Tool	Loads the reference for
`learn_statement_semantics`	The filter / statement query language used by audiences, campaign membership, and contact queries.
`learn_email_building`	The `EmailData` JSON shape (components, theme, layout, merge fields).
`learn_form_building`	The `FormData` JSON shape (components, hidden fields, theme, settings).
`learn_workflow_building`	The workflow graph (nodes, edges, triggers, control flow).

Call the matching skill tool before any tool that takes a body, design, statement, or filter argument. For example, load learn_email_building before create_email or update_email.

Not available over MCP

Not available	Notes
Sandbox and file tools	Running code, reading and writing files, and uploading images run only in the chat sandbox, which doesn’t exist over MCP. Your client’s own environment is separate from Conversion.
Sending, publishing, activating	Building or editing an asset never sends a blast, publishes a form, or activates a workflow. Those stay manual steps in Conversion.
Deleting	The MCP server cannot delete contacts, audiences, emails, forms, workflows, campaigns, folders, fields, or tokens.
Editing live workflows	Workflows are create-only (see above).

For why the sandbox is chat-only and what else differs, see Differences from chat.

​Reading and lookups

​Creating new assets

​Editing existing assets

​Campaigns and webinars

​Skill tools

​Not available over MCP

Reading and lookups

Creating new assets

Editing existing assets

Campaigns and webinars

Skill tools

Not available over MCP