LinkedIn: React to post
linkedin_react_to_postLike/react to a LinkedIn post as the connected person, or as a managed company page using react_as from linkedin_list_managed_company_pages. Use a supported LinkedIn reaction value and only when the user's intent to react is clear.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"post_id": "<post_id>",
"reaction": "<reaction>"
},
"name": "linkedin_react_to_post"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes | Exact provider post ID returned by post search/list/get. Never pass post text, author ID or URL. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it. | |
| react_as | No | Optional numeric CompanyPage.id from linkedin_list_managed_company_pages for the SAME account_id. Choose the page by name from that list; never use mailbox_id, inbox_id, a company URL/slug, name, URN or person ID. Omit to act as the connected person. Requires the company product enabled during account_connect and current page admin rights; company search alone does not prove access. Never omit this field as a fallback after a company action fails. | |
| reaction | Yes | LinkedIn reaction type (a plain 'like' or an emoji is rejected by LinkedIn). | |
| account_id | No | Optional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here. |