Send connection request
Send one outbound LinkedIn connection request (outward action). profile_id is the target URN (ln_id OR sn_id). Server-side checks run first: the daily send limit, the premium-aware note cap (200 free / 300 premium), and the 21-day resend cooldown. Fire-on-success: a row is created only when LinkedIn confirms the send. NOT idempotent: a second send while a request is pending 409s (already_pending).
Contract:
- MCP tool
send_linkedin_connection_request, registry packagemcp.linkedin/linkedin_connection_requests, mountlinkedin.network. - 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; step eligible: gtm.service.orchestration can run this verb as a mass-action plan step, once per item.
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_connection_request.
LinkedIn account sid (ln_ac_…) of the sending account.
18^ln_ac_Target URN: ln_id (ACoAA…) OR sn_id (ACwAA…); both accepted as profile_id.
Invitation note; server caps at 200 chars when the sender is not premium.
300Default false. Retry WITHOUT the note on a with-note cap failure.