> ## Documentation Index > Fetch the complete documentation index at: https://docs.linkedcamp.com/llms.txt > Use this file to discover all available pages before exploring further. # Leads and activities > Prospects, their history, and the individual scheduled actions that make up that history. Requires the **Campaigns** permission. Tools in this group are hidden from `tools/list` and refused on call when your plan does not grant it. | Tool | Kind | | - | - | | [`activity_list`](#activity_list) | Read-only | | [`activity_skip`](#activity_skip) | Write, Destructive | | [`lead_add`](#lead_add) | Write | | [`lead_blacklist`](#lead_blacklist) | Write, Destructive | | [`lead_delete`](#lead_delete) | Write, Destructive | | [`lead_export`](#lead_export) | Write | | [`lead_flow_state`](#lead_flow_state) | Read-only | | [`lead_get`](#lead_get) | Read-only | | [`lead_list`](#lead_list) | Read-only | | [`lead_move`](#lead_move) | Write | | [`lead_note_add`](#lead_note_add) | Write | | [`lead_note_update`](#lead_note_update) | Write, Destructive | | [`lead_notes_list`](#lead_notes_list) | Read-only | | [`lead_update`](#lead_update) | Write | ## activity\_list Read-only Completed actions — one row per lead per step. Only COMPLETED activities are returned; the upstream field cannot return PENDING or FAILED rows. To see a failure and its `failedReason`, read one lead with `lead_get`. Note that `status` here filters the LEAD's pipeline status, not the activity's. ### Parameters Campaign id, from `campaign_list` or `campaign_create`. Filters the LEAD pipeline status, not the activity status. Activities are always COMPLETED. Free-text search. Date window as \{ from, to } — epoch milliseconds or ISO 8601. Omit for the backend default. Start of the window. End of the window. Alias for `from`. Alias for `to`. 1-indexed page number. ## activity\_skip Write Destructive Marked destructive in the protocol — your MCP client asks for confirmation before running it. Mark one pending action SKIPPED, to unblock a lead stuck on a step that will never succeed. That status is the only thing it writes — it does not itself schedule the next step, so do not promise the lead has advanced; re-read with `lead_flow_state` to see what the flow does next. It acts on an activity id, not a lead id. To stop a lead entirely use `lead_update` with `paused` or `isExcluded`. ### Parameters Activity id, from `activity_list`. ## lead\_add Write Add one prospect to a campaign by LinkedIn profile URL and/or email. A lead needs at least one of those two — a row with neither is rejected. For more than a handful, use `campaign_upload_leads`. ### Parameters Campaign id, from `campaign_list` or `campaign_create`. linkedin.com/in/… profile URL. Required if there is no profile URL. Given name. Family name. Full display name. Use instead of first/last when you only have one string. Job title. City, region or country. Phone number. Website URL. Sales Navigator profile URL. LinkedIn Recruiter profile URL. Free-text hook available in copy as \{\{personalization}}. Extra merge fields, e.g. \{ "recentPost": "…" }, usable as \{\{recentPost}}. ## lead\_blacklist Write Destructive Marked destructive in the protocol — your MCP client asks for confirmation before running it. Add a lead to the blacklist: their sequence stops and they will be excluded from every future campaign on this account. The right response to an opt-out request. Account-wide and lasting, and no tool removes a blacklist entry — confirm the person and get an explicit yes before calling. To stop sending to someone without excluding them permanently, use `lead_update` with `isExcluded: true` instead. ### Parameters Lead id, from `lead_list`. ## lead\_delete Write Destructive Marked destructive in the protocol — your MCP client asks for confirmation before running it. Permanently remove leads from a campaign along with their pending actions. Irreversible — confirm with the user, and prefer `lead_update` with `isExcluded: true` when they only want sending to stop. ### Parameters Campaign id, from `campaign_list` or `campaign_create`. Specific leads to delete. Delete every lead matching a filter instead of an id list, e.g. \{ "status": "FAILED" }. ## lead\_export Write Generate a CSV of leads filtered by campaign, status and tags. Returns a filename served from the CDN. Use it when the user wants a file. To read leads in the conversation use `lead_list`; for campaign performance numbers rather than people, `campaign_export_stats`. ### Parameters Campaign id, from `campaign_list` or `campaign_create`. Filter by lead pipeline status. Tag ids to filter by, from `tag_list`. ## lead\_flow\_state Read-only Where a lead sits in its campaign sequence right now, when the next action fires, and whether it has been orphaned by a sequence edit. One lead, current position only. For every lead waiting on a given step use `sequence_leads_at_step`; for what a sequence rewrite did to the whole campaign use `flow_audit`. ### Parameters Lead id, from `lead_list`. ## lead\_get Read-only Full profile for one lead, plus its complete activity history and current position in the campaign flow — the single call to make when asked "what happened with this person". This is also the only place a FAILED action and its `failedReason` can be read: `activity_list` returns COMPLETED rows only. Do not page through `lead_list` to assemble one lead's history. ### Parameters Lead id, from `lead_list`. Include the per-step activity history. Include the full message thread. Can be long. ## lead\_list Read-only Prospects in a campaign (or across your whole account), with their current pipeline status. The list view: many leads, a few fields each. For one person's full story use `lead_get`, for where they are in the sequence `lead_flow_state`, and for a spreadsheet `lead_export`. Filter by `status` to answer questions like "who replied this week" (REPLIED) or "who accepted but never answered" (CONNECTED). ### Parameters Omit to search every campaign. Search name, email or company. Filter by pipeline status. Tag ids — leads must carry at least one. Date window as \{ from, to } — epoch milliseconds or ISO 8601. Omit for the backend default. Start of the window. End of the window. Alias for `from`. Alias for `to`. 1-indexed page number. Rows per page. ## lead\_move Write Transfer leads into a different campaign. Understand what the backend actually does before offering this, because it is not a relocation: it INSERTS a new lead row in the destination at status FOUND, clearing `acceptedAt` and `repliedAt`, schedules a fresh activity on the destination's first step, and soft-deletes the original with `deleteReason: "MOVED"`. So the prospect restarts from the beginning and the per-step history does not come along — inbox conversations do, they are repointed at the new row. A lead already in the destination by profile URL or email is skipped. The destination must have a LinkedIn account attached or it throws "Destination campaign has no LinkedAccount." — set one with `campaign_update` first. Beware `selectAll`: it moves every lead from the first listed lead's campaign and ignores the rest of the list. ### Parameters Destination campaign id. Lead ids, from `lead_list`. Move every lead matching the current filter rather than the id list. ## lead\_note\_add Write Write an internal note on a lead. Never sent to the prospect — this is not a way to message anyone, and sending an inbox message has no tool at all. Use `lead_note_update` to change one afterwards; it replaces the whole body. ### Parameters Lead id, from `lead_list`. Body text. ## lead\_note\_update Write Destructive Marked destructive in the protocol — your MCP client asks for confirmation before running it. Rewrite an existing internal note. Replaces the whole body — pass the full text, not a fragment, and read it with `lead_notes_list` first if you do not already have it. Editing a note changes nothing the prospect sees. ### Parameters Note id, from `lead_notes_list`. Body text. ## lead\_notes\_list Read-only Internal notes your team has written about a lead. Not visible to the prospect. Notes are free text for humans and have no effect on sending. For the messages actually exchanged with the prospect read `conversation_get`. ### Parameters Lead id, from `lead_list`. ## lead\_update Write Edit a lead: correct contact details, pause its sequence, exclude it from sending, or attach merge-field data. `paused: true` freezes just this lead; `isExcluded: true` takes it out of the campaign without deleting the record. Scope is one lead. It cannot pause a whole campaign — pausing a campaign has no tool and is web-app only — and it cannot move a lead elsewhere (`lead_move`) or change its tags for reply classification, which happens on the conversation via `conversation_update`. ### Parameters Lead id, from `lead_list`. Email address. Given name. Family name. Job title. Phone number. Website URL. Free-text hook for this person, available in copy as \{\{personalization}}. Freeze this lead's sequence without removing it. Remove from sending while keeping the record. Mark the reply as positive intent. Mark as read. Extra merge-field data, e.g. \{ "recentPost": "…" }, usable in copy as \{\{recentPost}}. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.