SalesTouch Docs
All MCP tools
Read onlyLinkedIn

Lead status

lead_status

Inspect a lead's LinkedIn and email outreach: contact dates, acceptance, and queued actions. Find it by LinkedIn profile, lead_id, or email. The email block lists its addresses, the last emails sent and received, and scheduled emails. invitation_status checks one target profile and local send guards without scanning all invitations. pending is confirmed; eligible means profile eligibility, not proof of invitation absence; unknown makes no claim about current invitation state. Previous uncertain sends and cooldown guards block sending. message tracks only the linkedin_invite_then_message follow-up. message.status=none does not mean no direct linkedin_message was sent; check last_contacted_at. queued is local scheduling only.

When to use it

Inspect one lead's mini-profile, CRM status, inbox status, tags, sources, relationship, follow-up, and queued-message state.

Required scopes
linkedin:accesssalestouch:use
Execution
Synchronous MCP tool call

Requirements

Provide lead_id, followup_id, or one LinkedIn member target.

Example

Ask your agent

Check the SalesTouch lead status for https://www.linkedin.com/in/example.

Tool arguments
{
  "linkedin_url": "https://www.linkedin.com/in/example"
}
MCP response envelope
{
  "content": [
    {
      "type": "text",
      "text": "{\n  \"data\": { ... },\n  \"meta\": null\n}"
    }
  ],
  "isError": false
}

Expected: The lead directory record together with its current relationship and outreach state.

Parameters

crm_scope
string

CRM scope: organization, member:<id>, or group:<id>. Defaults to your shared group or personal CRM.

account_id
string

Connected SalesTouch account id, username, email, handle, or account URL.

identifier
string

LinkedIn member handle, public id, account id, or profile URL.

lead_id
string

Canonical SalesTouch lead id returned by lead_status or leads_search.

followup_id
string

Optional invite-then-message follow-up id.

email
string

Lead email address. Finds a lead imported or emailed at that address.

Aliases are shown independently because MCP clients send a flat JSON object. Use one alias from each required group, not every alias.

Common errors

insufficient_scope

Reconnect the MCP and approve the requested LinkedIn permission.

paid_plan_required

Use a SalesTouch workspace with LinkedIn MCP access.

trial_payment_method_required

Add a payment method in SalesTouch billing to activate the trial and LinkedIn MCP access.

On this page

When to use itRequirementsExampleParametersCommon errorsRelated tools