Merge tag check
Static content may only use merge tags fromseamless://templates/variables. A templateData subject or body with any other bracketed tag (e.g. [Your Name], {company_size}) is rejected with an “Unknown merge fields” error that lists the tags; rewrite the copy with real values or available variables and retry. On create_campaign the whole call is rejected and nothing is created. aiPrompt content is not checked.
Access: Connect (full). See Access control.
list_campaigns
List campaigns, or get a specific campaign by ID/identifier. When campaignId or campaignIdentifier is provided, returns detailed campaign info including steps, schedule, and status. Otherwise returns a table of campaigns, newest first, with pagination metadata (total, nextCursor). Campaigns are filtered server-side: use status to target a lifecycle state (e.g. status: [“completed”] for finished campaigns) and cursor to page through the full set instead of scanning the first page.Arguments
Filter campaigns by lifecycle status (only used when listing). One or more of: completed, archived, paused, active, draft. Archived campaigns are excluded unless “archived” is requested.One of:
completed, archived, paused, active, draft.Result
Returns a textcontent block and a structuredContent object with these fields. Treat every field as nullable: a value the record does not have comes back as null.
Pagination metadata when available. Carries only the values the service has, so treat a missing key as unknown rather than zero; nextCursor is null or absent on the last page.
create_campaign
Create a new campaign. The recommended approach is to includesteps and contactIds inline rather than making separate create_campaign_step and add_contacts_to_campaign calls. For email campaigns (auto-email or manual-email steps), you MUST provide emailAccountIds so the campaign has a sending address. Use list_email_accounts or the seamless://email-accounts resource to get valid IDs. Steps are processed sequentially in order (same schema as create_campaign_step). On partial failure, successfully-created items are returned in the error context.
STEP CONTENT MODES: each step’s content comes from exactly one of:
- templateId — an existing saved template (see list_templates).
- templateData — a static template with [merge_tag] dynamic variables that you write now; the same copy is sent to every contact with the variables filled in.
- aiPrompt — instructions the AI runs for each contact when the step executes, producing unique content per contact. Plain instructions with NO merge tags or variables; the AI already has the contact’s profile. If the user’s request does not make the mode clear, ask whether they want a static template with dynamic variables or an AI prompt before creating the steps. When the user supplies the copy, or asks for merge tags, use templateData; when they ask for AI-written or per-contact personalized content, use aiPrompt. Do not call the tool with both.
- PLAIN TEXT ONLY. Never emit HTML tags such as <p>, </p>, <br>, <br/>, <div>, <a>, <span>. Never wrap paragraphs in tags. Never close with </p>. If you find yourself typing ”<”, stop and use a newline instead.
- NO sign-off line of any kind. Forbidden: “Best,”, “Thanks,”, “Regards,”, “Cheers,”, “Sincerely,”, followed by a name or anything else. The platform appends signatures automatically.
- NO invented placeholders. Forbidden examples: [pain_point], [value_prop], [Your Name], [First Name] — any token that is not on the available variable list. Saving a template or campaign step with an unknown tag fails with an error that lists the tags. Emails and drafts are not checked: unknown tags pass through unresolved and the recipient sees the literal text. Use ONLY square-bracket merge tags from seamless://templates/variables (e.g. [first_name], [company], [title]), or real values, or rewrite the sentence to omit the missing detail.
- Use exactly ONE blank line between sentences. A blank line is one empty line — never two or more.
Arguments
Email account IDs to link as sending addresses. Required before adding auto-email or manual-email steps. Use list_email_accounts to get valid IDs; an account whose sign-in has expired is rejected with expiredToken.
Campaign steps to create inline (preferred over separate create_campaign_step calls). Processed sequentially in order. Same schema as create_campaign_step (minus campaignId).
Per-day task limits for the inline steps: how many contacts may become due on each cadence day. dueDay must match a step and dailyTaskLimit must be a whole number of at least the number of steps on that day, otherwise the request fails. Days not listed receive the default for organizations on campaign send limits and stay unlimited for everyone else.
This campaign’s daily send limit on each linked email account (emailAccountId must be in emailAccountIds). Accounts not listed keep the default allocation.
Whether the per-day task limits apply (default false). Off means no daily task cap on any step; email steps still follow the inbox send limits. The stored dailyTaskLimits are kept.
Saved contact IDs (from get_my_contacts) to add inline (preferred over separate add_contacts_to_campaign calls). Added after steps are created.Up to 500 items.
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
Example
add_contacts_to_campaign
Add saved contacts to an EXISTING campaign. Prefer passing contactIds inline via create_campaign when building a new campaign. Use this tool only when adding contacts to a campaign that already exists. Rejected if the campaign is archived or deleted. Contact IDs must come from get_my_contacts, not from search results. Use research_contacts first to save contacts. Returns the updated campaign and contactsAdded, the number of contacts actually enrolled — this can be lower than the number requested when contacts are not in the org or fall below the campaign AI score threshold.Arguments
Array of saved contact IDs to add. Must be IDs from get_my_contacts, not search result IDs.Up to 500 items.
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
list_campaign_steps
List all steps in a campaign, including their type, status, delay, and template content. Returns a table of step details.Arguments
Result
Returns a textcontent block and a structuredContent object with these fields. Treat every field as nullable: a value the record does not have comes back as null.
Pagination metadata when available. Carries only the values the service has, so treat a missing key as unknown rather than zero; nextCursor is null or absent on the last page.
create_campaign_step
Add a new step to an EXISTING campaign. Prefer passing steps inline via create_campaign when building a new campaign. Use this tool only when adding steps to a campaign that already exists. For auto-email and manual-email steps, the campaign MUST have linked email accounts (set emailAccountIds via create_campaign or update_campaign first). For email steps, provide exactly one of templateId, templateData (static content with merge tags), or aiPrompt (AI writes personalized content per contact when the step runs); automatic email steps are rejected without one. Use template variables like [first_name], [company], [title] from the seamless://templates/variables resource for personalization. STEP CONTENT MODES: each step’s content comes from exactly one of:- templateId — an existing saved template (see list_templates).
- templateData — a static template with [merge_tag] dynamic variables that you write now; the same copy is sent to every contact with the variables filled in.
- aiPrompt — instructions the AI runs for each contact when the step executes, producing unique content per contact. Plain instructions with NO merge tags or variables; the AI already has the contact’s profile. If the user’s request does not make the mode clear, ask whether they want a static template with dynamic variables or an AI prompt before creating the steps. When the user supplies the copy, or asks for merge tags, use templateData; when they ask for AI-written or per-contact personalized content, use aiPrompt. Do not call the tool with both.
- PLAIN TEXT ONLY. Never emit HTML tags such as <p>, </p>, <br>, <br/>, <div>, <a>, <span>. Never wrap paragraphs in tags. Never close with </p>. If you find yourself typing ”<”, stop and use a newline instead.
- NO sign-off line of any kind. Forbidden: “Best,”, “Thanks,”, “Regards,”, “Cheers,”, “Sincerely,”, followed by a name or anything else. The platform appends signatures automatically.
- NO invented placeholders. Forbidden examples: [pain_point], [value_prop], [Your Name], [First Name] — any token that is not on the available variable list. Saving a template or campaign step with an unknown tag fails with an error that lists the tags. Emails and drafts are not checked: unknown tags pass through unresolved and the recipient sees the literal text. Use ONLY square-bracket merge tags from seamless://templates/variables (e.g. [first_name], [company], [title]), or real values, or rewrite the sentence to omit the missing detail.
- Use exactly ONE blank line between sentences. A blank line is one empty line — never two or more.
Arguments
The type of campaign step. For auto-email and manual-email, the campaign must have linked email accounts.One of:
manual-email, auto-email, call, linkedin-message, linkedIn, linkedin-connect-request, custom.Day number from campaign start to execute this step (e.g. 1 = first day, 4 = day four, 7 = day seven). Must be >= 1.
ID of an existing template to use for this step. Cannot be combined with templateData or aiPrompt.
Inline static template content. Creates a hidden template for this step. Cannot be combined with templateId or aiPrompt. Use template variables from seamless://templates/variables for personalization.
Instructions for the AI to write this step’s content for EACH contact when the step runs, instead of a fixed template. Use when the user wants AI-generated, per-contact personalization (e.g. “reference their industry and a recent company news item”). PLAIN TEXT instructions only: describe the goal, value proposition, tone, call to action and length. Do NOT write the email/message itself and do NOT include HTML. Do NOT include merge tags or variables (e.g. [first_name], [company]) — the AI receives the contact’s full profile and personalizes from it; say “address them by first name”, not a tag. For email steps the AI writes both the subject and the body. Cannot be combined with templateId or templateData. Each contact generation consumes AI credits.
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
update_campaign_step
Update an existing campaign step. Modify its name, delay, content, or position. Content can be switched to a saved template (templateId), static inline content (templateData), or an AI prompt (aiPrompt) — provide exactly one. Returns the updated step. STEP CONTENT MODES: each step’s content comes from exactly one of:- templateId — an existing saved template (see list_templates).
- templateData — a static template with [merge_tag] dynamic variables that you write now; the same copy is sent to every contact with the variables filled in.
- aiPrompt — instructions the AI runs for each contact when the step executes, producing unique content per contact. Plain instructions with NO merge tags or variables; the AI already has the contact’s profile. If the user’s request does not make the mode clear, ask whether they want a static template with dynamic variables or an AI prompt before creating the steps. When the user supplies the copy, or asks for merge tags, use templateData; when they ask for AI-written or per-contact personalized content, use aiPrompt. Do not call the tool with both.
- PLAIN TEXT ONLY. Never emit HTML tags such as <p>, </p>, <br>, <br/>, <div>, <a>, <span>. Never wrap paragraphs in tags. Never close with </p>. If you find yourself typing ”<”, stop and use a newline instead.
- NO sign-off line of any kind. Forbidden: “Best,”, “Thanks,”, “Regards,”, “Cheers,”, “Sincerely,”, followed by a name or anything else. The platform appends signatures automatically.
- NO invented placeholders. Forbidden examples: [pain_point], [value_prop], [Your Name], [First Name] — any token that is not on the available variable list. Saving a template or campaign step with an unknown tag fails with an error that lists the tags. Emails and drafts are not checked: unknown tags pass through unresolved and the recipient sees the literal text. Use ONLY square-bracket merge tags from seamless://templates/variables (e.g. [first_name], [company], [title]), or real values, or rewrite the sentence to omit the missing detail.
- Use exactly ONE blank line between sentences. A blank line is one empty line — never two or more.
Arguments
Day number from campaign start to execute this step (e.g. 1 = first day, 4 = day four). Must be >= 1.
ID of a template to use for this step. Cannot be combined with templateData or aiPrompt.
Updated inline static template content. Cannot be combined with templateId or aiPrompt. Use template variables from seamless://templates/variables for personalization.
Replaces the step content with an AI prompt. Instructions for the AI to write this step’s content for EACH contact when the step runs, instead of a fixed template. Use when the user wants AI-generated, per-contact personalization (e.g. “reference their industry and a recent company news item”). PLAIN TEXT instructions only: describe the goal, value proposition, tone, call to action and length. Do NOT write the email/message itself and do NOT include HTML. Do NOT include merge tags or variables (e.g. [first_name], [company]) — the AI receives the contact’s full profile and personalizes from it; say “address them by first name”, not a tag. For email steps the AI writes both the subject and the body. Cannot be combined with templateId or templateData. Each contact generation consumes AI credits.
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
delete_campaign_step
Delete a draft step from a campaign. Remaining steps are automatically renumbered. Returns the deleted step and the remaining steps with their new step numbers. This cannot be undone.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
start_campaign
Start a draft campaign so it begins working its contacts and sending its email steps. Only a draft campaign can be started. The campaign must have: (1) a schedule, (2) at least one linked email account if it has email steps, (3) at least one contact, (4) at least one step, and (5) an email template on every unfinished automatic email step. Starting also requires the user to have accepted the Engage Terms of Service in the Seamless.AI app. Confirm with the user before calling. Returns the campaign ID and new status.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
pause_campaign
Pause an active campaign. No further steps run or emails send until it is resumed with resume_campaign. Returns the campaign ID and new status.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
resume_campaign
Resume a paused campaign so it continues working its contacts and sending its email steps. Only a paused campaign can be resumed. The campaign must have: (1) a schedule, (2) at least one linked email account if it has email steps, (3) at least one contact, (4) at least one step, and (5) an email template on every unfinished automatic email step. Starting also requires the user to have accepted the Engage Terms of Service in the Seamless.AI app. Confirm with the user before calling. Returns the campaign ID and new status.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
complete_campaign
Mark an active campaign as completed, ending it for all contacts. A completed campaign cannot be started, resumed, or archived again. Confirm with the user before calling. Returns the campaign ID and new status.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
archive_campaign
Archive a draft, active, or paused campaign, stopping it and hiding it from the active campaign list. Restore it to draft with unarchive_campaign. Returns the campaign ID and new status.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
unarchive_campaign
Restore an archived campaign to draft. It does not resume sending; call start_campaign afterward to run it again. Returns the campaign ID and new status.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
list_campaign_contacts
List contacts in a campaign with their engagement status and current step. Returns a paginated table.Arguments
Result
Returns a textcontent block and a structuredContent object with these fields. Treat every field as nullable: a value the record does not have comes back as null.
Pagination metadata when available. Carries only the values the service has, so treat a missing key as unknown rather than zero; nextCursor is null or absent on the last page.
remove_contacts_from_campaign
Remove specific contacts from a campaign. Returns the updated campaign and contactsRemoved, the number of contacts actually removed — this is 0 when none of the IDs are currently enrolled. This does not delete the contacts themselves.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
get_campaign_metrics
Get per-step engagement metrics for a campaign. Returns emails sent, opened, bounced, replied, and calls made per step.Arguments
Result
Returns a textcontent block and a structuredContent object. Its fields are the record’s own and vary by record; treat every field as nullable.
pause_campaign_step
Pause an in-progress step of a campaign. Its tasks stop running until the step is resumed with resume_campaign_step. The campaign must not be completed, archived, or deleted. Returns the step ID and new status.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
resume_campaign_step
Resume a paused campaign step so its tasks run again, including any email sends. The campaign must not be completed, archived, or deleted. Confirm with the user before calling. Returns the step ID and new status.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
skip_campaign_step
Skip an in-progress or paused campaign step, so its remaining tasks are skipped for every contact. The campaign must not be completed, archived, or deleted. Confirm with the user before calling. Returns the step ID and new status.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
clone_campaign
Create a copy of an existing campaign with a new name. Copies steps and configuration but not contacts. Email account links may need to be re-added via update_campaign. Returns the new campaign.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
update_campaign
Update an existing campaign name, visibility settings, linked email accounts, per-account daily send limits, per-day task limits, or the daily task limit switch (isDailyTaskLimitEnabled). Email accounts MUST be linked before adding auto-email or manual-email steps. Use list_email_accounts or the seamless://email-accounts resource to get valid emailAccountIds. Daily send limits, task limits and the switch can be changed in any campaign state and take effect at once (an active campaign moves contacts between active and pending to fit); email accounts can be added in any state, but removing one from an active campaign fails with 422 campaignActive: pause the campaign first with pause_campaign, then resume it with resume_campaign. Returns the updated campaign with its dailySendLimits, dailyTaskLimits and isDailyTaskLimitEnabled.Arguments
Email account IDs to link to this campaign for sending. Use list_email_accounts to get valid IDs; an account whose sign-in has expired is rejected with expiredToken unless it is already linked. Required before adding auto-email or manual-email steps.
This campaign’s daily send limit on linked email accounts. Accounts not listed keep their current limit; unlinked accounts are rejected (link them via emailAccountIds first).
Per-day task limits: how many contacts may become due on each cadence day. dueDay must match a step and dailyTaskLimit must be a whole number of at least the number of steps on that day; a day with an email step cannot exceed the summed dailySendLimit of every linked account, connected or not (dailySendCapacity counts only connected ones). Can be changed in any campaign state and takes effect at once.
Whether the per-day task limits apply. Off means no daily task cap on any step; email steps still follow the inbox send limits. The stored dailyTaskLimits are kept; a change takes effect at once in any campaign state.
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
delete_campaign
Permanently delete a campaign and all its associated steps and tasks. This cannot be undone. Use list_campaigns to find campaign IDs.Arguments
Result
Returns a textcontent block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.