All tools

Prospecting · send_linkedin_message

Send LinkedIn message

Send a LinkedIn message or invitation (Unipile or the user's Chrome).

Price
included
Requirements
LinkedIn (Unipile) or LinkedIn (Chrome)
set it up in Settings → Integrations
Human approval
Yes, by default
outside-facing write: a human validates

Input

FieldTypeDescription
messagesarrayBatch send: the FULL list of LinkedIn messages/invites to send in one call (preferred whenever there is more than one recipient). Each item takes the same fields as a single message. When provided, the top-level single-message fields are ignored.
linkedinUrlstringRecipient's full LinkedIn profile URL (e.g. https://www.linkedin.com/in/john-doe). Optional in browser mode when recipientName is given: the user's Chrome finds the profile itself — NEVER search LinkedIn with the browser tools.
message *stringPersonalised message text. Max 300 chars for connection requests. Use first name and company name.
typemessage | connection_request | autoDefault "auto": the sender checks the profile — connected → direct message, otherwise invitation with the text as note. Set "message" or "connection_request" only when the user said which one. Never ask the user.
recipientNamestringRecipient's full name (e.g. 'Jean Dupont'). Required when linkedinUrl is omitted.
accountIdstringUnipile account ID for the LinkedIn account to use (auto-detected if not provided)

Call this tool

Through the HTTP API, or from the MCP server with the run meta-tool.

curl https://api.ezyagents.fr/gateway/v1/run \
  -H "Authorization: Bearer ezk_…" -H "Content-Type: application/json" \
  -d '{"tool":"send_linkedin_message","input":{"messages":[],"linkedinUrl":"…","message":"…","type":"message"}}'
$run({ "tool": "send_linkedin_message", "input": {"messages":[],"linkedinUrl":"…","message":"…","type":"message"} })