Send LinkedIn message
Send one outbound regular LinkedIn DM on the basic messenger (outward action). Reply to an existing thread via linkedin_conversation_sid, or open a new thread to a 1st-degree connection via ln_id / sn_id. Guards run first: in-flight dedup, send_messages daily cap, 8000-char body cap, connection guard, attachment https:// reachability, basic-messenger surface guard. Fire-on-success: a row is inserted only on terminal success. When NOT: InMail to a non-connection → send_linkedin_inmail; voice note → send_linkedin_voice_message; Sales Navigator thread → send_linkedin_sales_nav_message; the connection-request note lives on linkedin-connection-requests. Bulk send: loop client-side and respect the daily cap.
Contract:
- MCP tool
send_linkedin_message, registry packagemcp.linkedin/linkedin_messages, mountlinkedin.messaging. - Operation
action, response envelopeaction. - Flags: dangerous: the MCP layer gates it behind a preview/commit token, and the effect cannot be undone through this API.
Authorizations
Access token issued by gtm.service.id. Its access_identity claim carries team_sid, actor_sid and actor_type, and that team scope is authoritative.
Team scope for tokens that do not carry one. Ignored when the token already names a team.
Body
Request body of send_linkedin_message.
LinkedIn account sid (ln_ac_…).
18^ln_ac_Message body; 1..8000 chars.
1 - 8000Existing basic-messenger thread; provide this OR a profile URN.
18^ln_cv_Regular-profile URN (ACoAA…) for a new thread.
128Sales Navigator URN (ACwAA…); interchangeable with ln_id.
64Each .path must be an https:// URL.