LinkedIn API-based operations: publish posts/articles/carousels, fetch metrics, fetch comments, get profile, and reply via API. For browser-based actions (browsing the feed, engaging in the browser, scraping the UI) use the `browse` skill instead.
linkedin 5 BST per callWhat it does
LinkedIn-specific actions through the official Graph API. Publish posts, articles, and carousels; reply to comments; pull metrics and your profile data. Each action maps to one connector call — the agent doesn't reason about whether `action='thread'` is valid for LinkedIn (it isn't).
When to use it
Brandstaq automatically picks LinkedIn when you say things like:
- “Publish this draft to LinkedIn now”
- “Get LinkedIn metrics for the post I shared yesterday”
- “Reply to the top comment on our pricing post”
- “Pull the comments thread on the Q2 launch announcement”
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| tags | array | No | — |
| limit | integer | No | — |
| title | string | No | — |
| action | string | Yes | Linkedin operation to perform. Each value maps to a connector method; mismatched action/params return UNKNOWN_ACTION. |
| caption | string | No | Post caption. |
| content | string | No | — |
| post_id | string | No | — |
| parent_id | string | No | — |
| media_path | string | No | Local path or R2 key for the media. |
| media_type | string | No | — |
| visibility | string | No | — |
| media_paths | array | No | — |
| since_cursor | string | No | — |
| canonical_url | string | No | — |
| content_format | string | No | — |
| featured_image_url | string | No | — |
When the agent reaches for it
When you mention LinkedIn explicitly — publish a post there, reply to a comment, pull metrics for your page — the agent picks this skill. Each action (publish, reply, get_metrics, etc.) maps to one official Graph API call, so behavior is predictable.