Automate LinkedIn Posts and Profile Management

Automates LinkedIn operations - creating posts, uploading and attaching images, commenting, deleting posts, and retrieving profile/company info - through Composio's LinkedIn toolkit exposed via Rube MCP. It documents exact tool sequences, required parameters, and the URN-format and rate-limit pitfalls needed to drive LinkedIn correctly.

Use this skill when a task requires publishing a LinkedIn text post, uploading/attaching images to a post, commenting on an existing post, deleting a post, or retrieving profile/company information. It assumes Rube MCP is already connected (RUBE_SEARCH_TOOLS available) and the LinkedIn connection is ACTIVE via RUBE_MANAGE_CONNECTIONS - always call RUBE_SEARCH_TOOLS first for current schemas.

Setup: add https://rube.app/mcp as an MCP server (no API keys needed), verify RUBE_SEARCH_TOOLS responds, call RUBE_MANAGE_CONNECTIONS with toolkit linkedin, complete the LinkedIn OAuth link if not ACTIVE.

Five core workflows: Create a post - LINKEDIN_GET_MY_INFO first to get the user's URN, LINKEDIN_REGISTER_IMAGE_UPLOAD if attaching media, then LINKEDIN_CREATE_LINKED_IN_POST with text and explicit visibility ('PUBLIC' or 'CONNECTIONS'), since character limits and visibility defaults require explicit handling. Get profile info - LINKEDIN_GET_MY_INFO (authenticated user only, cannot look up others) and LINKEDIN_GET_COMPANY_INFO (requires the numeric organization ID, not a company name or vanity URL). Manage post images - a two-phase upload: LINKEDIN_REGISTER_IMAGE_UPLOAD to get an upload URL and asset URN, upload the image binary to that URL, optionally verify via LINKEDIN_GET_IMAGES, then use the asset URN when creating the post. Comment on posts - LINKEDIN_CREATE_COMMENT_ON_POST with a valid post URN and an actor URN matching the authenticated user or a managed organization, respecting comment rate limits. Delete a post - LINKEDIN_DELETE_LINKED_IN_POST, which is permanent and restricted to the post author or organization admin.

Common patterns: resolving a user URN (urn:li:person:...) from GET_MY_INFO for use as actor/owner in subsequent calls, resolving an organization URN from GET_COMPANY_INFO for posting as a company page, and the image upload flow (register, upload binary, verify, then post with the asset URN).

Known pitfalls preserved from the source: LinkedIn OAuth tokens have limited scopes and expire, so 401 errors mean re-authentication is needed; URNs must always be used in full format (e.g. urn:li:person:ABC123), never just the alphanumeric ID, and organization URNs differ from person URNs; LinkedIn enforces strict daily rate limits on posts and comments, requiring backoff and respect for Retry-After headers on 429 responses; and post content has API-enforced character limits with no HTML markup support.

Runs entirely through Rube MCP (https://rube.app/mcp) and Composio's LinkedIn toolkit - RUBE_SEARCH_TOOLS for schema discovery and RUBE_MANAGE_CONNECTIONS for the LinkedIn OAuth connection, with no separate LinkedIn developer app management required.

Social media and growth teams and automation builders who need to publish, manage, and engage with LinkedIn posts through Composio/Rube MCP tools correctly - especially around the URN format, two-phase image upload, and strict rate limits that are easy to get wrong from the raw LinkedIn API alone.