How to connect Seamless MCP with OpenClaw

Search the Seamless.AI database for contacts matching filters like company, title, seniority, and location. At least one filter (or savedSearchId) is required; a call with none is rejected rather than returning an empty page. Returns a paginated table of matching contacts. Costs 1 credit per 50 results returned, rounded up; a page is trimmed to the rows the remaining credits cover. For contacts you have already saved, use get_my_contacts instead.

Search the Seamless.AI database for companies matching filters like name, domain, industry, size, and revenue. Returns a paginated table of matching companies. Costs 1 credit per 50 results returned, rounded up; a page is trimmed to the rows the remaining credits cover. For companies you have already saved, use get_my_companies instead.

Search the location vocabulary for the exact spellings a location filter will match, most common first. Use this whenever you are unsure how the data spells a place, and before setting any location filter on search_contacts, search_companies, or a saved search: spellings follow the data rather than the local exonym (Germany's state is "Bavaria", not "Bayern"), and a value the vocabulary does not hold is rejected. Each result carries the contact count behind it, which is what disambiguates a name that means several places ("Ontario" is a Canadian province and five US cities), and a type naming which filter the value belongs on. US state abbreviations and country aliases like "TX" and "USA" are accepted by the filters directly and need no lookup.

Research (enrich) contacts to get verified emails, phone numbers, job history, and other data. Consumes credits. Provide searchResultIds from a previous search_contacts call OR a contacts array. Set waitForResults: true to auto-poll up to 30s; otherwise returns requestIds to use with poll_contact_research. Researched contacts are saved and can be retrieved with get_my_contacts. Pass listIds to file every newly saved contact into those contact lists — use get_lists to find an existing list, or create_list first for a new one. Contacts that were already researched are not re-saved, so add those to a list with update_my_contact instead. The saved contact IDs from get_my_contacts are required for add_contacts_to_campaign and other engagement tools.

Poll for contact research results. Pass requestIds from research_contacts. Returns each result with a status: done, error, missing, or not found. Poll again if any results are not in a terminal status. A done result carries the enriched contact, including jobHistory — the contact's prior roles as companyName/title/startedAt/endedAt, most recent departure first, and an empty array when none are known.

Research (enrich) companies to get verified details like revenue, size, and technologies. Consumes credits. Provide searchResultIds from a previous search OR a companies array. Set waitForResults: true to auto-poll up to 30s; otherwise returns requestIds to use with poll_company_research.

Poll for company research results. Pass requestIds from research_companies. Returns each result with a status: done, error, or missing. Poll again if any results are not in a terminal status.

Consumes credits upfront for every requested result; unused credits are restored when the run finishes or is cancelled. Before calling, confirm with the user the run name, how many results to research (the total from the search you just ran is the ceiling; caps 10,000 contacts / 5,000 companies), and whether to add saved contacts to lists (listIds from get_lists) or auto-import to a connected CRM (autoImportToCrm; skip the question unless seamless://me shows a CRM). Reuse the exact filters from the search the user just ran, or pass savedSearchId. One Autopilot per type runs at a time; cancel with tasks/cancel or cancel_autopilot.

Returns status and progress for an Autopilot (automated search) run. Prefer tasks/get for runs started as an MCP task.

Returns presigned download URLs for Autopilot result CSV files. URLs expire in 300 seconds; call again for fresh links. Never streams file content.

Cancel a running Autopilot. Irreversible; the current batch may finish before the run stops. Already-researched records are kept and unused credits are restored within a few minutes. For a run started as an MCP task, tasks/cancel is equivalent. Confirm with the user before calling.

Get current credit balance and usage for the authenticated user. The seamless://credits resource provides the same data. When linking to the Seamless web app, use the applicationBaseUrl from seamless://me as the root; never invent hostnames such as app.seamless.ai.

Retrieve previously saved/researched contacts for the authenticated user within a date range (max 30 days). Defaults to the last 30 days if no dates are provided. Returns a paginated table. Use search_contacts to find new contacts in the Seamless.AI database.

Update saved contacts. Currently manages which lists they belong to: listAction "add" (default) keeps existing lists, "remove" drops only the supplied lists, and "replace" makes the supplied lists their complete set of lists. Contact IDs come from get_my_contacts (or the contactId of an already saved search_contacts result); list IDs from get_lists or create_list. Returns the contacts that changed, plus skippedContactIds for any that did not — check it before reporting success. To file contacts into a list as part of researching them, pass listIds to research_contacts instead.

Retrieve previously saved/researched companies for the authenticated user within a date range (max 30 days). Defaults to the last 30 days if no dates are provided. Returns a paginated table. Use search_companies to find new companies in the Seamless.AI database.

Update saved companies. Currently manages which lists they belong to: listAction "add" (default) keeps existing lists, "remove" drops only the supplied lists, and "replace" makes the supplied lists their complete set of lists. Company IDs come from get_my_companies; list IDs from get_lists or create_list. Returns the companies that changed, plus skippedCompanyIds for any that did not — check it before reporting success.

List saved searches, or get a specific saved search by ID. When id is provided, returns that saved search with its filter values. Otherwise returns a table of all saved searches.

Save a set of search filters as a named saved search for later reuse. Returns the created saved search with its ID.

Update an existing saved search name, filters, or sort options. Returns the updated saved search. When values is provided it replaces the saved filters wholesale rather than merging with the existing filters.

Permanently delete a saved search by its ID. This cannot be undone. Use list_saved_searches to find saved search IDs.

List all contact lists, or get a specific list by ID. When listId is provided, returns that list with contact count. Otherwise returns a table of all lists. To add saved contacts or companies to one of these lists, pass its listId to update_my_contact or update_my_company.

Create a new contact list. Returns the created list with its ID. Lists organize saved contacts: add contacts that are already saved by passing the new list ID to update_my_contact, or pass it to research_contacts as listIds to file contacts into the list as they are researched. Never leave a new list empty when the user asked for it to be populated.

Rename an existing contact list. Returns the updated list.

Permanently delete a contact list. This removes the list but does not delete the contacts in it. Use get_lists to find list IDs.

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, hasMore). Campaigns are filtered server-side: use status to target a lifecycle state (e.g. status: ["completed"] for finished campaigns) and offset to page through the full set instead of scanning the first page.

Create a new campaign. The recommended approach is to include `steps` 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. MCP REINFORCEMENTS (these override and clarify the base rules — read first): - 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. Unknown tags are not rejected: they pass through unresolved and the recipient sees the literal text. Use ONLY curly-brace 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. Output ONLY subject and body. "Subject:" prefix, blank line, then body. Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: "Hey Sarah," or "Hi David," Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don't know. If an [About Me] profile is provided, it describes the sender. Use it to accurately represent the sender. Never apply the sender's name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don't disclose that the information is missing in the output. Just omit it.

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.

List all steps in a campaign, including their type, status, delay, and template content. Returns a table of step details.

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. MCP REINFORCEMENTS (these override and clarify the base rules — read first): - 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. Unknown tags are not rejected: they pass through unresolved and the recipient sees the literal text. Use ONLY curly-brace 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. Output ONLY subject and body. "Subject:" prefix, blank line, then body. Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: "Hey Sarah," or "Hi David," Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don't know. If an [About Me] profile is provided, it describes the sender. Use it to accurately represent the sender. Never apply the sender's name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don't disclose that the information is missing in the output. Just omit it.

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. MCP REINFORCEMENTS (these override and clarify the base rules — read first): - 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. Unknown tags are not rejected: they pass through unresolved and the recipient sees the literal text. Use ONLY curly-brace 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. Output ONLY subject and body. "Subject:" prefix, blank line, then body. Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: "Hey Sarah," or "Hi David," Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don't know. If an [About Me] profile is provided, it describes the sender. Use it to accurately represent the sender. Never apply the sender's name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don't disclose that the information is missing in the output. Just omit it.

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.

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.

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.

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.

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.

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.

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.

List contacts in a campaign with their engagement status and current step. Returns a paginated table.

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.

Get per-step engagement metrics for a campaign. Returns emails sent, opened, bounced, replied, and calls made per 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.

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.

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.

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.

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.

Permanently delete a campaign and all its associated steps and tasks. This cannot be undone. Use list_campaigns to find campaign IDs.

List email templates, or get a specific template by ID. When templateId is provided, returns that template with subject, body, and metadata. Otherwise returns a paginated table of templates. The seamless://templates resource provides a quick list without pagination. See seamless://templates/variables for available merge tag variables.

Create a new email template with subject and body content. Use template variables like {first_name}, {company}, {title} for personalization — read seamless://templates/variables for all available merge tags. Returns the created template with its ID. Use list_email_footers to find footer IDs. MCP REINFORCEMENTS (these override and clarify the base rules — read first): - 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. Unknown tags are not rejected: they pass through unresolved and the recipient sees the literal text. Use ONLY curly-brace 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. Output ONLY subject and body. "Subject:" prefix, blank line, then body. Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: "Hey Sarah," or "Hi David," Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don't know. If an [About Me] profile is provided, it describes the sender. Use it to accurately represent the sender. Never apply the sender's name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don't disclose that the information is missing in the output. Just omit it.

Update an existing email template name, subject, or body. Use template variables like {first_name}, {company} for personalization (see seamless://templates/variables). Returns the updated template. MCP REINFORCEMENTS (these override and clarify the base rules — read first): - 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. Unknown tags are not rejected: they pass through unresolved and the recipient sees the literal text. Use ONLY curly-brace 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. Output ONLY subject and body. "Subject:" prefix, blank line, then body. Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: "Hey Sarah," or "Hi David," Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don't know. If an [About Me] profile is provided, it describes the sender. Use it to accurately represent the sender. Never apply the sender's name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don't disclose that the information is missing in the output. Just omit it.

Permanently delete an email template by its ID. This cannot be undone. Use list_templates to find template IDs.

List connected email accounts for the authenticated user. Returns available sender addresses that can be used for sending emails and campaigns. The seamless://email-accounts resource provides the same data without pagination.

Create an email draft for a contact. The draft is saved but not sent until you call send_email_draft. Returns the draft with its ID. Use list_email_accounts or seamless://email-accounts to find valid sender addresses. Use template variables like {first_name}, {company} for personalization (see seamless://templates/variables). MCP REINFORCEMENTS (these override and clarify the base rules — read first): - 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. Unknown tags are not rejected: they pass through unresolved and the recipient sees the literal text. Use ONLY curly-brace 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. Output ONLY subject and body. "Subject:" prefix, blank line, then body. Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: "Hey Sarah," or "Hi David," Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don't know. If an [About Me] profile is provided, it describes the sender. Use it to accurately represent the sender. Never apply the sender's name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don't disclose that the information is missing in the output. Just omit it.

Retrieve a previously created email draft by its ID. Returns the draft content and metadata.

Update the content of an existing email draft before sending. Returns the updated draft. MCP REINFORCEMENTS (these override and clarify the base rules — read first): - 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. Unknown tags are not rejected: they pass through unresolved and the recipient sees the literal text. Use ONLY curly-brace 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. Output ONLY subject and body. "Subject:" prefix, blank line, then body. Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: "Hey Sarah," or "Hi David," Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don't know. If an [About Me] profile is provided, it describes the sender. Use it to accurately represent the sender. Never apply the sender's name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don't disclose that the information is missing in the output. Just omit it.

Send a previously created email draft. The email will be sent immediately. Does not consume search/research credits. Use create_email_draft first to create the draft.

Send an email directly to a contact in one step (creates and sends immediately). Does not consume search/research credits. Use template variables like {first_name}, {company} for personalization (see seamless://templates/variables). For more control, use create_email_draft + send_email_draft instead. MCP REINFORCEMENTS (these override and clarify the base rules — read first): - 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. Unknown tags are not rejected: they pass through unresolved and the recipient sees the literal text. Use ONLY curly-brace 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. Output ONLY subject and body. "Subject:" prefix, blank line, then body. Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: "Hey Sarah," or "Hi David," Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don't know. If an [About Me] profile is provided, it describes the sender. Use it to accurately represent the sender. Never apply the sender's name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don't disclose that the information is missing in the output. Just omit it.

Send emails to multiple contacts matching filter criteria. filters must include at least one of lists, contactIds, campaignIds, or a text query — an empty filter set is rejected so the whole book is never mailed. Resolves the audience first and rejects the request if more than 500 contacts match — the send is not truncated. Opted-out and unsubscribed contacts are skipped. Does not consume public API credits. Pass idempotencyKey so a retry of the same request returns the original job. Reusing a key with a different audience or message is rejected. Use template variables like {first_name}, {company} for personalization (see seamless://templates/variables). Returns jobId plus matched, queued, and skipped counts. MCP REINFORCEMENTS (these override and clarify the base rules — read first): - 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. Unknown tags are not rejected: they pass through unresolved and the recipient sees the literal text. Use ONLY curly-brace 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. Output ONLY subject and body. "Subject:" prefix, blank line, then body. Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: "Hey Sarah," or "Hi David," Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don't know. If an [About Me] profile is provided, it describes the sender. Use it to accurately represent the sender. Never apply the sender's name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don't disclose that the information is missing in the output. Just omit it.

Log a call outcome for a contact. Records the result of a call made outside the platform (not a click-to-call feature). Use list_call_dispositions and list_call_sentiments to get valid IDs.

List available call disposition options (e.g. "Left Voicemail", "Connected") for the organization. Use the returned IDs when calling log_call.

List available call sentiment options (e.g. "Positive", "Neutral", "Negative") for the organization. Use the returned IDs when calling log_call.

Get the engagement activity feed showing email opens, replies, bounces, calls, and other events. Returns a paginated list of activity events.

List tasks, or get a specific task by ID. When taskId is provided, returns detailed task info including status, contact, and campaign details. Otherwise returns a paginated table of tasks with optional filters.

Run a to-do or scheduled task now. For an automatic email task this sends the email immediately. Confirm with the user before calling. Returns the task ID and the action taken.

Pause a to-do, scheduled, or errored task so it does not run until it is unpaused with unpause_task. Returns the task ID and the action taken.

Unpause a paused task so it is due again. A campaign email task can send once it is due. Confirm with the user before calling. Returns the task ID and the action taken.

Mark a to-do, paused, scheduled, or errored task as completed, for example after the user made the call or did the work themselves. This does not send anything. Returns the task ID and the action taken.

Skip a to-do, paused, pending, scheduled, or errored task so it is not done for this contact. Confirm with the user before calling. Returns the task ID and the action taken.

Cancel a task that has not finished, so it never runs. Confirm with the user before calling. Returns the task ID and the action taken.

Create a standalone task (email, call, or custom action) for a contact. This is separate from campaign steps — use create_campaign_step for campaign workflows. Returns the created task with its ID.

Update an existing task. Modify its name, due date, description, priority, or status. Returns the updated task.

Permanently delete a task. This cannot be undone. Use list_tasks to find task IDs.

List email footers available to the authenticated user for use in campaigns and templates. Returns a paginated list of footers with their IDs. The seamless://connect/config resource includes related engagement settings.

Send a preview of an email to a specified address for review before launching a campaign. Typically used to send to yourself. Does not send to contacts or consume credits.