Available tools

Find the Acquisity MCP tool for campaigns, leads, sequences and results.

Acquisity exposes 24 MCP tools. Your assistant chooses a tool from your request, then supplies its arguments. The tools use the same permissions and validation as the API reference.

Start with list_workspaces. Pass the chosen workspaceId to other tools; get_operation takes an operationId instead.

Workspaces and campaign results

Tool	What it does
`list_workspaces`	Lists the workspaces your key can access.
`get_workspace`	Reads one workspace's details.
`list_campaigns`	Lists campaigns in a workspace.
`get_campaign`	Reads a campaign and its current state.
`get_campaign_metrics`	Reads performance metrics.
`validate_campaign`	Checks campaign readiness and reports missing setup. Provider-side launch checks can still reject a launch.

Use workspaces:read for workspace tools and campaigns:read for campaign reads and validation.

Campaign changes

These tools require a workspace key with campaigns:write.

Tool	What it does
`create_campaign`	Creates a draft. Does not launch it; configured campaign-created automations may run.
`update_campaign`	Changes supported campaign settings. Requires `ifMatch` from the latest `get_campaign` response's `updatedAt`.
`duplicate_campaign`	Creates a draft copy. Provider duplication and lead import can continue asynchronously.
`launch_campaign`	Starts or resumes real outreach. Can send email and spend money.
`pause_campaign`	Requests a pause to future sending; cannot recall messages already handed off.
`set_campaign_sequence`	Attaches an exact or AI-generated sequence to a draft without an existing sequence.
`copy_campaign_sequence`	Replaces a draft's sequence with a copy from another campaign.

For set_campaign_sequence, supply either exact steps or an AI brief with niche and emailMethod. AI generation requires the workspace's cold-email and niche-research setup; the direct method also needs its direct-method setup. To edit individual steps, use the app. The API read model does not return sequence content, so review the sequence in Acquisity before launching.

Read the latest campaign before updating it. If another change makes ifMatch stale, read it again before retrying. Campaign creation guide.

Campaign leads

Tool	What it does	Required scope
`list_campaign_leads`	Lists leads already in a campaign.	`campaignLeads:read`
`get_campaign_lead`	Reads one campaign lead.	`campaignLeads:read`
`export_campaign_leads`	Exports existing leads as paginated CSV.	`campaignLeads:read`
`preview_campaign_lead_search`	Counts matching leads and returns a redacted sample without spending credits.	`campaigns:write`, workspace key
`ai_search_campaign_leads`	Turns a brief into proposed filters for review. Does not run the search or spend credits.	`campaigns:write`, workspace key
`search_campaign_leads`	Runs a paid search and attaches matching leads to the campaign.	`campaigns:write`, workspace key

export_campaign_leads returns up to 3,000 records per page. Follow its returned nextCursor until there is no next page; the cursor is in a separate JSON content block alongside the CSV.

Adding leads to an active campaign enrols them in its live sequence. Preview first and confirm the target campaign before running a paid search.

Standalone lead search

These tools work in a workspace without attaching results to a campaign. All require a workspace key.

Tool	What it does	Required scope
`ai_search_leads`	Proposes filters from a brief, without searching or spending credits.	`leads:read`
`preview_lead_search`	Shows match counts and a redacted sample without spending credits.	`leads:read`
`search_leads`	Runs a paid search and exports verified results. Does not change a campaign.	`leads:search`

Both paid search tools require an idempotencyKey. Reuse the same key and arguments for a retry; a new key can start another billed search.

Webhooks and operations

Tool	What it does
`create_webhook`	Registers an HTTPS destination for events. Requires `webhooks:write`; personal-token users must also be workspace owners or admins. Save the signing secret when it is returned, because it is shown once.
`get_operation`	Checks an asynchronous operation using its ID. Workspace-owned operations accept a key from the same workspace; user-owned operations require a token belonging to the same user.

When a tool says it is still running

Write tools wait briefly for an operation to finish. They can return before the work is complete. Always inspect the operation's status and keep its id.

For queued or running, call get_operation with the returned ID. Do not submit the original change again just because it is still running.
For failed, cancelled or needs_attention, read the returned error and any suggested fix.
A polling timeout or failure can still include the accepted operation's ID and links. Use those to check what happened before retrying.

For campaign lead search, succeeded means the search was dispatched. Leads may take several more minutes to appear; check list_campaign_leads afterward.

For standalone lead search, succeeded means search and verification have finished. The result includes downloadUrl, leadCount, format and expiresAt. Download before the link expires.

Each underlying request, including operation checks, consumes API quota. Read the operations guide.