add_leads_to_campaign

Move leads this account owns into a campaign this account owns, by explicit id. Updates membership only — sends nothing. Opted-out and suppressed leads are REJECTED with per-lead skip reasons even when listed explicitly; leads already in the target are deduplicated; the response includes the campaign's final lead count read back from the database. To pick the audience by filter instead of by id, use select_and_attach_leads (same attach semantics, driven by search_leads filters). If the target campaign was already reviewed, its earlier approval is stale (the launch step recounts recipients and refuses a token approved for a smaller audience), so a fresh review_campaign_readiness is required before launching.

Argument	Type	Description
lead_ids*	array	Lead ids to move (from find_lead, list_leads or search_leads).
campaign_id*	string	The destination campaign.
idempotency_key	string	Optional but recommended. Retrying the same key returns the same result instead of re-running the move; reusing it with different arguments is rejected as idempotency_conflict.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "campaign_id",
    "lead_ids"
  ],
  "properties": {
    "lead_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Lead ids to move (from find_lead, list_leads or search_leads)."
    },
    "campaign_id": {
      "type": "string",
      "description": "The destination campaign."
    },
    "idempotency_key": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional but recommended. Retrying the same key returns the same result instead of re-running the move; reusing it with different arguments is rejected as idempotency_conflict."
    }
  },
  "additionalProperties": false
}

analyze_lead_source

Summarise the leads in an account or one campaign: how many exist, how many can actually be contacted, how many opted out, and how they break down by status and source. Read-only — sends nothing and changes nothing. Start here when the operator asks what they have to work with.

read-only

Argument	Type	Description
campaign_id	string	Limit to one campaign. Omit to cover every campaign this account owns.

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "campaign_id": {
      "type": "string",
      "description": "Limit to one campaign. Omit to cover every campaign this account owns."
    }
  },
  "additionalProperties": false
}

attach_leads_to_campaign

Attach leads this account owns to a campaign this account owns, by explicit id. Synonym for add_leads_to_campaign — same tool, same behavior, same response shape, just the verb some callers expect. Updates membership only — sends nothing. Opted-out and suppressed leads are REJECTED with per-lead skip reasons even when listed explicitly; leads already in the target are deduplicated; the response includes the campaign's final lead count read back from the database. To pick the audience by filter instead of by id, use select_and_attach_leads (same attach semantics, driven by search_leads filters). If the target campaign was already reviewed, its earlier approval is stale (the launch step recounts recipients and refuses a token approved for a smaller audience), so a fresh review_campaign_readiness is required before launching.

Argument	Type	Description
lead_ids*	array	Lead ids to move (from find_lead, list_leads or search_leads).
campaign_id*	string	The destination campaign.
idempotency_key	string	Optional but recommended. Retrying the same key returns the same result instead of re-running the move; reusing it with different arguments is rejected as idempotency_conflict.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "campaign_id",
    "lead_ids"
  ],
  "properties": {
    "lead_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Lead ids to move (from find_lead, list_leads or search_leads)."
    },
    "campaign_id": {
      "type": "string",
      "description": "The destination campaign."
    },
    "idempotency_key": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional but recommended. Retrying the same key returns the same result instead of re-running the move; reusing it with different arguments is rejected as idempotency_conflict."
    }
  },
  "additionalProperties": false
}

check_campaign_readiness

Read-only, idempotent campaign readiness status for monitoring and scheduled checks: recipient count, message, channels, cost and every pass/warn/fail check. SENDS NOTHING and NEVER mints an approval token or confirmation phrase, so it cannot launch a campaign. Use review_campaign_readiness only when a human is actively deciding whether to launch.

read-only

Argument	Type	Description
lead_ids	array	Check a subset of the campaign's leads. Omit for all of them.
campaign_id*	string	The campaign to check.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "campaign_id"
  ],
  "properties": {
    "lead_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Check a subset of the campaign's leads. Omit for all of them."
    },
    "campaign_id": {
      "type": "string",
      "description": "The campaign to check."
    }
  },
  "additionalProperties": false
}

clone_campaign_draft

Copy a previous campaign's configuration (channel, message template, AI instructions, follow-up sequence, sender/automation settings) onto a brand-new campaign, and attach an audience to it. THE RESULT IS ALWAYS A DRAFT — this tool NEVER launches, NEVER sends, and never touches an approval token; it does not call launch_approved_campaign under any circumstance. import_ids (from preview_lead_import / import_leads_from_file) is the preferred way to supply a bulk audience — give several to combine multiple imported files into one campaign; leads are deduplicated across every import_id and lead_id given. At least one of import_ids/lead_ids should normally be supplied, or the clone has no audience. Use channels=['sms'] when the new draft must be text-only with no AI/voice calls, and from_address_id to pin the verified email identity on an email clone. After this, call review_campaign_readiness; only an explicit human approval may lead to launch_approved_campaign.

Argument	Type	Description
name*	string	Name for the new draft campaign.
subject	string	Optional email subject for the cloned message template (email/both clones only). Omit to copy the source template's subject, if it has one.
channels	array	Optional explicit channel narrowing on the new draft. Example: ['sms'] makes an SMS campaign text-only and prevents AI/voice calling. This can only narrow the campaign type, never widen it.
lead_ids	array	Existing lead ids to include (from find_lead/list_leads). May be combined with import_ids; deduplicated together.
import_ids	array

create_campaign_draft

Create a campaign in draft status with its opening SMS. THIS SENDS NOTHING — a draft cannot deliver a message. It exists so a human can read the exact wording and audience before deciding. The message is rejected if it implies a prior relationship or manufactures urgency. After this, call review_campaign_readiness.

Argument	Type	Description
name*	string	A name the operator will recognise in their dashboard.
message*	string	The opening SMS, 320 characters or fewer. Say who is writing and why. Do not imply a prior conversation or a deadline. An opt-out line is appended automatically on first contact.
subject	string	Optional email subject, stored with the message and carried onto an email clone of this draft. One line, 200 characters or fewer, no {{variables}}. Email campaigns otherwise get a subject at send time; only a prepared exact-message campaign must store one.
lead_ids	array	Existing leads to move into this campaign. Ids outside this account are ignored.
description	string	Context for the operator: who this targets and why.
idempotency_key	string	Repeat a retried call safely — the same key returns the same campaign.
outreach_vertical	string

create_lead

Add a single lead to a campaign this account owns. Requires campaign_id plus at least a phone or an email; deduplicates against the account's existing leads by contact detail. Writes a record only — sends nothing, to nobody, ever.

Argument	Type	Description
name	string	Full name, if first/last are not given separately.
email	string
notes	string
phone	string	Any common format; at least one of phone/email is required.
last_name	string
first_name	string
campaign_id*	string	The campaign this lead belongs to (required — every lead lives in a campaign).
company_name	string

Input schema (JSON)

{
  "type": "object",
  "required": [
    "campaign_id"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Full name, if first/last are not given separately."
    },
    "email": {
      "type": "string"
    },
    "notes": {
      "type": "string"
    },
    "phone": {
      "type": "string",
      "description": "Any common format; at least one of phone/email is required."
    },
    "last_name": {
      "type": "string"
    },
    "first_name": {
      "type": "string"
    },
    "campaign_id": {
      "type": "string",
      "description": "The campaign this lead belongs to (required — every lead lives in a campaign)."
    },
    "company_name": {
      "type": "string"
    }
  },
  "additionalProperties": false
}

find_lead

Search this account's leads by phone number, email address, or name. Phone matching tolerates formatting differences. Returns masked contact details plus lead ids. Read-only — sends nothing and changes nothing.

read-only

Argument	Type	Description
query*	string	A phone number, an email address, or part of a name.
campaign_id	string	Optional: narrow the search to one campaign.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "A phone number, an email address, or part of a name."
    },
    "campaign_id": {
      "type": "string",
      "description": "Optional: narrow the search to one campaign."
    }
  },
  "additionalProperties": false
}

get_campaign_status

Report recorded campaign outcomes: leads, sent records, confirmed delivery receipts, replies, opt-outs, booking records, and AI-paused leads (not people awaiting a human). Omit campaign_id to list campaigns. Account totals are independent of pagination and status filters. Read-only. Null metrics are unavailable; read the caveats before telling the operator a campaign is or is not working.

read-only

Argument	Type	Description
limit	integer
offset	integer
status	string	Filter the list by status, e.g. 'active', 'draft', 'paused'.
campaign_id	string	One campaign. Omit to list all of them.

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    },
    "status": {
      "type": "string",
      "description": "Filter the list by status, e.g. 'active', 'draft', 'paused'."
    },
    "campaign_id": {
      "type": "string",
      "description": "One campaign. Omit to list all of them."
    }
  },
  "additionalProperties": false
}

get_interested_leads

List leads whose replies were classified as positive or as asking a question, newest first, with the reply text. The classifier is keyword and sentiment based, NOT a language model — the response says so explicitly, and the reply text is included so you can judge for yourself. Read-only.

read-only

Argument	Type	Description
days	integer	How far back to look, in days (1-365). Default 30.
limit	integer
offset	integer
campaign_id	string	Limit to one campaign.

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 365,
      "minimum": 1,
      "description": "How far back to look, in days (1-365). Default 30."
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    },
    "campaign_id": {
      "type": "string",
      "description": "Limit to one campaign."
    }
  },
  "additionalProperties": false
}

get_performance_summary

The account's performance report, identical to the website's Performance page: pipeline (discovered, purchased, enriched, imported, duplicates excluded), readiness (prepared, approved, eligible at last launch), delivery (queued, provider-accepted, confirmed delivered, failed, unsettled -- never folded together), engagement (replies, interested, appointments, conversions), cost in credits, and one row per autopilot lane. Read-only; sends nothing and buys nothing. A null value means NOT MEASURED and carries an unavailable_reason -- never report it to the operator as zero.

read-only

Argument	Type	Description
lane	string	Narrow to one autopilot lane: 'base' or a Revenue Autopilot profile id. Not with campaign_id.
range	string	Reporting window. Default 30d.
campaign_id	string	Narrow to one of your campaigns. Not with lane.

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "lane": {
      "type": "string",
      "description": "Narrow to one autopilot lane: 'base' or a Revenue Autopilot profile id. Not with campaign_id."
    },
    "range": {
      "enum": [
        "30d",
        "7d",
        "90d",
        "all"
      ],
      "type": "string",
      "description": "Reporting window. Default 30d."
    },
    "campaign_id": {
      "type": "string",
      "description": "Narrow to one of your campaigns. Not with lane."
    }
  },
  "additionalProperties": false
}

import_leads_from_file

Upsert leads from an uploaded CSV or XLSX file into this account. WRITES TO THE DATABASE — SENDS NOTHING on any channel, ever; this only stores contacts. Deduplicates by phone/email (dedupe_by, default both) against both the file itself and every lead already in this account. Re-importing a lead that is opted-out, suppressed, or do-not-contact NEVER clears those flags and NEVER moves the lead — only genuinely new contacts are created. Returns an import_id: pass it to clone_campaign_draft's import_ids to attach this audience to a campaign. idempotency_key is required — retrying the same key returns the same result rather than importing twice; reusing it with different arguments is rejected as idempotency_conflict.

Argument	Type	Description
file*	object	The uploaded lead file, inline. filename + content_base64 (raw file bytes, base64-encoded) — this server's transport is stateless JSON-RPC with no separate attachment channel, so the file rides in the tool call itself. .csv and .xlsx only; 15MB decoded max.
mode	string	Import mode. Only 'upsert' (create new, update existing) is currently supported.
tags	array	Optional labels applied to every imported/updated lead.
source	string	Where this list came from, e.g. 'PropStream export'. Stored as provenance and never overwritten on re-import.
dedupe_by	array	Which normalized fields count as a duplicate match. Default: ["phone", "email"] (either matching is a duplicate).
column_mapping

launch_approved_campaign

SENDS REAL MESSAGES TO REAL PEOPLE. This is irreversible and costs credits. It requires an approval_token from review_campaign_readiness and explicit operator authorization for this exact launch. In an interactive current turn where the human explicitly asked to send this campaign, pass operator_authorized_this_launch=true instead of asking them to copy/paste the server phrase. Never set that flag for a scheduled or background run, standing instructions, prior approval, enthusiasm, or inferred intent. Never infer approval. Never generate the confirmation yourself. The exact confirmation phrase remains supported for other clients. Never reuse an approval issued for a different campaign or a different size.

destructive

Argument	Type	Description
channel	string	Must match the channel the readiness review approved. Default 'sms'; 'email' launches email-only.
lead_ids	array	Must match the subset that was reviewed and approved.
campaign_id*	string	The campaign to launch.
from_number	string	SMS channel only: the same outbound number the readiness review was run with. Omit for automatic sender routing.
confirmation	string	The exact confirmation phrase from the readiness review. Optional only when operator_authorized_this_launch=true.
approval_token

list_from_addresses

The verified email sender identities (from-addresses) this account can send campaigns from. Read-only; sends nothing. Use before an email-channel readiness review to pick the right sender.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

list_leads

Page through this account's leads, optionally filtered by campaign and status. Read-only — sends nothing and changes nothing. For richer filtering (geography, source, tags, contact history, SMS eligibility), use search_leads — the same data with the audience-building filter vocabulary.

read-only

Argument	Type	Description
limit	integer
offset	integer
status	string	Optional lead status filter, e.g. 'active'.
campaign_id	string	Optional: one campaign only.

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    },
    "status": {
      "type": "string",
      "description": "Optional lead status filter, e.g. 'active'."
    },
    "campaign_id": {
      "type": "string",
      "description": "Optional: one campaign only."
    }
  },
  "additionalProperties": false
}

pause_campaign

Stop a campaign from sending anything further. Queued messages that have not yet gone out are skipped; anything already handed to the carrier cannot be recalled. Safe to call when unsure — pausing is reversible and errs toward not contacting people.

Argument	Type	Description
reason	string	Why it is being paused, for the operator's records.
campaign_id*	string	The campaign to pause.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "campaign_id"
  ],
  "properties": {
    "reason": {
      "type": "string",
      "maxLength": 500,
      "description": "Why it is being paused, for the operator's records."
    },
    "campaign_id": {
      "type": "string",
      "description": "The campaign to pause."
    }
  },
  "additionalProperties": false
}

preview_lead_import

Inspect an uploaded CSV or XLSX lead file WITHOUT writing anything to the database — read-only, sends nothing. Auto-detects common columns (name, phone, email, address, company/entity name) and reports row counts, in-file and account duplicates, missing contact fields, and how many leads would end up SMS- and email-contactable. Run this before import_leads_from_file so the operator can see what would happen first.

read-only

Argument	Type	Description
file*	object	The uploaded lead file, inline. filename + content_base64 (raw file bytes, base64-encoded) — this server's transport is stateless JSON-RPC with no separate attachment channel, so the file rides in the tool call itself. .csv and .xlsx only; 15MB decoded max.
dedupe_by	array	Which normalized fields count as a duplicate match. Default: ["phone", "email"] (either matching is a duplicate).
column_mapping	object	Optional override of auto-detected columns: {target_field: 'exact column name in the file'}. Target fields: first_name, last_name, full_name, phone, mobile_phone, email, address, property_address, city, state, zip, company_name. Anything not given here falls back to auto-detection.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "file"
  ],
  "properties": {
    "file": {
      "type": "object",
      "required": [
        "filename",
        "content_base64"
      ],
      "properties": {
        "filename": {
          "type": "string",
          "maxLength": 255,
          "description": "Original filename, e.g. 'alameda_investors.xlsx'. Determines .csv vs .xlsx parsing."
        },
        "content_base64": {
          "type": "string",
          "description": "The raw file bytes, base64-encoded."
        }
      },
      "description": "The uploaded lead file, inline. filename + content_base64 (raw file bytes, base64-encoded) — this server's transport is stateless JSON-RPC with no separate attachment channel, so the file rides in the tool call itself. .csv and .xlsx only; 15MB decoded max.",
      "additionalProperties": false
    },
    "dedupe_by": {
      "type": "array",
      "items": {
        "enum": [
          "phone",
          "email"
        ],
        "type": "string"
      },
      "description": "Which normalized fields count as a duplicate match. Default: [\"phone\", \"email\"] (either matching is a duplicate)."
    },
    "column_mapping": {
      "type": "object",
      "description": "Optional override of auto-detected columns: {target_field: 'exact column name in the file'}. Target fields: first_name, last_name, full_name, phone, mobile_phone, email, address, property_address, city, state, zip, company_name. Anything not given here falls back to auto-detection.",
      "additionalProperties": {
        "type": "string"
      }
    }
  },
  "additionalProperties": false
}

recommend_followup_campaign

Propose how to follow up, based on which leads have never been contacted, were contacted without replying, or already replied. Returns segments with counts and a suggested approach for each. Read-only — this is a proposal to discuss with the operator, not a plan that has been put into effect.

read-only

Argument	Type	Description
goal	string	What the operator is trying to achieve, in their words.
campaign_id	string	Limit to one campaign. Omit to cover the whole account.

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "goal": {
      "type": "string",
      "maxLength": 500,
      "description": "What the operator is trying to achieve, in their words."
    },
    "campaign_id": {
      "type": "string",
      "description": "Limit to one campaign. Omit to cover the whole account."
    }
  },
  "additionalProperties": false
}

review_campaign_readiness

Pre-flight a campaign: how many people would be contacted, on which channels, what it would cost, and which checks pass, warn or fail. SENDS NOTHING. If everything passes, it returns a short-lived approval token and a confirmation phrase — both of which a human operator must authorise before launch_approved_campaign will do anything. Run this before every launch; the token is single-use and campaign-specific.

read-only

Argument	Type	Description
channel	string	How the campaign goes out. Default 'sms' (text + voice where applicable). 'email' reviews an email-only launch.
lead_ids	array	Review a subset of the campaign's leads. Omit for all of them.
campaign_id*	string	The campaign to review.
from_number	string	SMS channel only: an approved outbound number for this account. Omit for automatic sender routing.
from_address_id	string	Email channel only: the sender identity to send from (see list_from_addresses). Omit to use the account default.
all_textable_numbers	boolean	SMS only. When true, approve one separate text to every eligible textable phone on each selected lead. Used by DealFinder's attended Send-to-all action.

search_leads

Search this account's leads by campaign/list, source, geography (city/state/county), lead type, tags, contact history (never_contacted / contacted_no_reply / replied) and SMS eligibility (textable phone, not opted out, not suppressed), with paging and a deterministic sort. Returns lead_id values plus masked contact details and per-lead eligibility flags. Read-only — SENDS NOTHING and changes nothing. This is the filter-rich sibling of list_leads (plain paging) and find_lead (locate one person); use the lead_ids it returns with add_leads_to_campaign, or let select_and_attach_leads run the same filters and attach a bounded subset in one step.

read-only

Argument	Type	Description
city	string	Exact city, case-insensitive.
sort	string	Deterministic orders (ties broken by id). Default 'newest'.
tags	array	Leads carrying ANY of these tags.
limit	integer	Page size, max 200. Default 25.
state	string	Exact state, case-insensitive, e.g. 'CA'.
county	string	Exact county, case-insensitive.
offset	integer
source

select_and_attach_leads

Deterministically select up to requested_count SMS-eligible leads matching the same filters search_leads accepts (nested under 'filters') and attach them to a DRAFT campaign this account owns — the same membership move add_leads_to_campaign performs, driven by a filter instead of an id list. SENDS NOTHING and never launches. Opted-out and suppressed leads are never selected; leads already in the target are skipped. best_eligible orders by score (highest first) then newest, so the same request against the same data selects the same leads; the response lists the exact ids attached, the eligible total, and an honest shortfall when fewer matched than requested. Attaching to a reviewed campaign makes its earlier approval stale (the launch step recounts recipients and refuses a token approved for a smaller audience), so review_campaign_readiness must run again — and then STOP for the human operator.

Argument	Type	Description
filters	object	Same vocabulary as search_leads. filters.campaign_id = the source campaign/list to select FROM.
campaign_id*	string	The DRAFT campaign to attach to. Must be owned by this account and have status 'draft'.
idempotency_key*	string	Required. Retrying the same key returns the same selection instead of attaching twice; reusing it with different arguments is rejected.
requested_count*	integer	Exactly this many leads when enough are eligible; fewer (with an honest shortfall report) when not.
selection_strategy	string

update_campaign_message

Rewrite the opening SMS of a campaign that is still a DRAFT. THIS SENDS NOTHING — it changes stored wording only, and it never launches or enqueues anything. DRAFT ONLY: a campaign that has already launched is refused, because editing it mid-send would tell one half of an audience something different from the other; clone it into a new draft instead. The replacement is held to the same rules as create_campaign_draft — 320 characters, and rejected if it implies a prior relationship or manufactures urgency. IT INVALIDATES PRIOR APPROVALS: any approval token issued before the edit stops working, because the launch check covers the message body. Run review_campaign_readiness again afterwards and get a fresh human approval before any launch.

Argument	Type	Description
message*	string	The replacement opening SMS, 320 characters or fewer. Say who is writing and why. Do not imply a prior conversation or a deadline. An opt-out line is appended automatically on first contact, so do not write one into the message.
subject	string	Optional replacement email subject. Omit to keep the stored subject. One line, 200 characters or fewer, no {{variables}}. Changing it also voids prior approvals.
campaign_id*	string	The DRAFT campaign whose opening message should change. Must be owned by this account.
idempotency_key	string	Recommended. Repeat a retried call safely — the same key with the same message replays the first result; the same key with a different message is refused.

Input schema (JSON)

PersuadioAI

Try it

add_leads_to_campaign

PersuadioAI

Try it

add_leads_to_campaign

Tools (22)