Omeda MCP - Email | Omeda Platform Knowledge Base

Omeda MCP is coming soon. This page describes how the email tools work once it's available.

To connect Omeda to your AI assistant, see Omeda MCP Overview.

The email tools report on deployments in your active database, and create, edit and test deployments built through the connector. Nothing goes to your audience from the assistant: scheduling, approval and the live send happen only in the Omeda platform. Setting a deployment date through the connector doesn't schedule or approve the send.

What you can do

Ask in plain language. The assistant picks the right tools and tells you which deployments and date ranges it used.

You want to	Try asking
Check how a send performed	"How did yesterday's Daily Brief perform? Opens, clicks and unsubscribes."
Compare sends over a period	"Rank last month's newsletters by click rate and flag anything well below the rest."
Find deployments	"What's scheduled to go out this week?"
Understand who clicked	"Which companies and job titles clicked most in deployment ACME261020005?"
Review content	"List the article headlines and links in this morning's newsletter."
Start a new deployment	"Clone last Tuesday's Daily Brief for next Tuesday at 6 AM Central."
Update content	"Change the subject line to 'Your week in aviation' and update the preheader to match."
Add an audience	"Add the 'Daily Brief Subscribers' audience query to this deployment."
Test before approval	"Send a test to the testers on this deployment."

Clicker breakdowns by company, job title and location cover the unique clickers who have that information on file, not your whole audience. Some lists show only the top values, and companies and titles appear as people entered them.

When a build is done, open the deployment in Omeda to review, approve and schedule it.

Approvals and safeguards

Under default settings, the assistant asks for your approval before running email_deployment_update, email_deployment_set_content, email_deployment_add_audience, email_deployment_remove_audience and email_deployment_send_test, since each changes an existing deployment or sends email. Creating or cloning a deployment doesn't need tool approval by default, but the assistant may still ask for missing details, such as a name, date or deployment type, or confirm what you want before it acts. Your assistant's permission settings can change these defaults. See the Omeda MCP Overview.

Rules the tools enforce:

Changes to an existing deployment only work on deployments created through the connector. Deployments built in the Omeda platform can be read but not edited through the connector.
New and cloned deployments must have a date in the future.
A clone keeps the original deployment's final approver.

How the assistant works with you:

It asks you to choose the deployment type and to confirm the audience query by name before using them.
When you clone a deployment, it tells you who the final approver is.

Good to know

Changes work on single-split deployments. The connector reports on multi-split deployments, and creates, clones and edits single-split deployments. Performance is reported for the deployment as a whole, not per split.
No journeys or A/B tests. Deployments built here are standalone Email Builder deployments. Journeys are built in Journeys in the Omeda platform.
Uses your saved audience queries. The connector attaches saved Audience Builder queries. Building or editing a query happens in Audience Builder.
Central time. Dates and times you enter and see through the connector are in Central time (America/Chicago). The assistant converts to your time zone when it knows it, and confirms the Central time before setting a deployment date.
Reporting updates nightly. Performance figures come from Omeda's nightly reporting. A deployment sent today may not show results until tomorrow, and the assistant tells you when deployments are left out for that reason.
Audience attachment takes time. Attaching an audience runs in the background and can take several minutes for large audiences.
Large reports are paged. Searches and rollups return up to 200 deployments at a time. The assistant pages through the rest when it needs them.

Troubleshooting

What you see	What to do
The assistant says it can't edit a deployment	Edits only work on single-split deployments created through the connector. For a single-split deployment built in Omeda, ask the assistant to clone it and edit the copy. For a multi-split deployment, make the change in the Omeda platform.
A content update returns an error	The change may still have saved. Ask the assistant to look up the deployment and check its modification history before trying again.
An audience is still attaching after 15 minutes	Large audiences can take longer. Check back later, or open the deployment in Omeda to see its status.
A deployment is missing from a performance report	Its nightly reporting may not have run yet. The assistant reports how many deployments were left out for this reason. For large reports, it may not list every one.
A date is rejected	New and cloned deployments need a future date in Central time.

Tool reference

You don't need tool names to use the connector. This list is for reference, for example when you set tool permissions in your assistant.

Read tools

Tool	What it does
`account_context_describe`	Shows who you are signed in as, the active database, and the databases you can access
`email_deployment_search`	Finds deployments by name, date range, status, designation, type or owner
`email_deployment_lookup`	Returns one deployment's settings, status, performance totals, link clicks and clicker breakdowns
`email_deployment_aggregate_lookup`	Rolls up performance across many sent deployments, with per-deployment rows for comparison (defaults to the last 60 days)
`email_deployment_content_lookup`	Returns a deployment's body content, either parsed into headlines, links and descriptions or as raw HTML
`email_deployment_type_lookup`	Lists the deployment types in the active database
`email_deployment_defaults_lookup`	Shows the default from name, mailbox and testers for a deployment type
`audience_query_search`	Finds saved Audience Builder queries by name
`email_audience_assignment_status`	Reports whether an audience has finished attaching to a deployment
`email_workflow_describe`	Gives the assistant the recommended order of steps for building a deployment
`tool_manifest_describe`	Lists the connector's tools and their versions

Tools that make changes

Tool	What it does
`database_select`	Switches the active database for the conversation
`email_deployment_create`	Creates a new, empty deployment
`email_deployment_clone`	Copies an existing deployment's content, sender, links and testers into a new deployment (the audience is not copied)
`email_deployment_update`	Changes a deployment's name, date, notes or testers
`email_deployment_set_content`	Sets the subject line, preheader, from name, mailbox, reply-to and HTML or text body
`email_deployment_add_audience`	Attaches a saved Audience Builder query to a deployment
`email_deployment_remove_audience`	Removes the audience from a deployment
`email_deployment_send_test`	Sends a test copy to the deployment's testers

Get help

For questions about the connector, your access or a result that looks wrong, see Get help in the Omeda MCP Overview.

Table of Contents