fetch_post
Retrieve LinkedIn post data, including comments and reactions, by supplying the post URL.
Instructions
Open a LinkedIn post and retrieve its data, with optional comments and reactions. (st.openPost action).
Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work.
A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| postUrl | Yes | LinkedIn URL of the post. (e.g., 'https://www.linkedin.com/posts/username_activity-id') | |
| retrieveComments | No | Optional. When true, also retrieve comments for the post. Configure via commentsRetrievalConfig. | |
| retrieveReactions | No | Optional. When true, also retrieve reactions for the post. Configure via reactionsRetrievalConfig. | |
| commentsRetrievalConfig | No | Optional. Applies only when retrieveComments is true. Controls comments retrieval (limit, replies, sort). | |
| reactionsRetrievalConfig | No | Optional. Applies only when retrieveReactions is true. Controls reactions retrieval (limit). |