LinkedIn Automation via Rube MCP

Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
• Active LinkedIn connection via

  RUBE_MANAGE_CONNECTIONS

  with toolkit

  linkedin

• Always call

  RUBE_SEARCH_TOOLS

  first to get current tool schemas

Setup

https://rube.app/mcp

1. Verify Rube MCP is available by confirming

   RUBE_SEARCH_TOOLS

   responds
2. Call

   RUBE_MANAGE_CONNECTIONS

   with toolkit

   linkedin

3. If connection is not ACTIVE, follow the returned auth link to complete LinkedIn OAuth
4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Create a LinkedIn Post

1. LINKEDIN_GET_MY_INFO

   - Get authenticated user's profile info [Prerequisite]

2. LINKEDIN_REGISTER_IMAGE_UPLOAD

   - Register image upload if post includes an image [Optional]

3. LINKEDIN_CREATE_LINKED_IN_POST

   - Publish the post [Required]

• text

  : Post content text

• visibility

  : 'PUBLIC' or 'CONNECTIONS'

• media_title

  : Title for attached media

• media_description

  : Description for attached media

• Must retrieve user profile URN via GET_MY_INFO before creating a post
• Image uploads require a two-step process: register upload first, then include the asset in the post
• Post text has character limits enforced by LinkedIn API
• Visibility defaults may vary; always specify explicitly

2. Get Profile Information

1. LINKEDIN_GET_MY_INFO

   - Get authenticated user's profile [Required]

2. LINKEDIN_GET_COMPANY_INFO

   - Get company page details [Optional]

• No parameters needed for GET_MY_INFO (uses authenticated user)

• organization_id

  : Company/organization ID for GET_COMPANY_INFO

• GET_MY_INFO returns the authenticated user only; cannot look up other users
• Company info requires the numeric organization ID, not the company name or vanity URL
• Some profile fields may be restricted based on OAuth scopes granted

3. Manage Post Images

1. LINKEDIN_REGISTER_IMAGE_UPLOAD

   - Register an image upload with LinkedIn [Required]
2. Upload the image binary to the returned upload URL [Required]

3. LINKEDIN_GET_IMAGES

   - Verify uploaded image status [Optional]

4. LINKEDIN_CREATE_LINKED_IN_POST

   - Create post with the image asset [Required]

• owner

  : URN of the image owner (user or organization)

• image_id

  : ID of the uploaded image for GET_IMAGES

• The upload is a two-phase process: register then upload binary
• Image asset URN from registration must be used when creating the post
• Supported formats typically include JPG, PNG, and GIF
• Large images may take time to process before they are available

4. Comment on Posts

1. LINKEDIN_CREATE_COMMENT_ON_POST

   - Add a comment to a post [Required]

• post_id

  : The URN or ID of the post to comment on

• text

  : Comment content

• actor

  : URN of the commenter (user or organization)

• Post ID must be a valid LinkedIn URN format
• The actor URN must match the authenticated user or a managed organization
• Rate limits apply to comment creation; avoid rapid-fire comments

5. Delete a Post

1. LINKEDIN_DELETE_LINKED_IN_POST

   - Delete the specified post [Required]

• post_id

  : The URN or ID of the post to delete

• Deletion is permanent and cannot be undone
• Only the post author or organization admin can delete a post
• The post_id must be the exact URN returned when the post was created

Common Patterns

ID Resolution

1. Call LINKEDIN_GET_MY_INFO
2. Extract user URN (e.g., 'urn:li:person:XXXXXXXXXX')
3. Use URN as actor/owner in subsequent calls

1. Call LINKEDIN_GET_COMPANY_INFO with organization_id
2. Extract organization URN for posting as a company page

Image Upload Flow

• Call REGISTER_IMAGE_UPLOAD to get upload URL and asset URN
• Upload the binary image to the provided URL
• Use the asset URN when creating a post with media
• Verify with GET_IMAGES if upload status is uncertain

Known Pitfalls

• LinkedIn OAuth tokens have limited scopes; ensure required permissions are granted
• Tokens expire; re-authenticate if API calls return 401 errors

• LinkedIn uses URN identifiers (e.g., 'urn:li:person:ABC123')
• Always use the full URN format, not just the alphanumeric ID portion
• Organization URNs differ from person URNs

• LinkedIn API has strict daily rate limits on post creation and comments
• Implement backoff strategies for bulk operations
• Monitor 429 responses and respect Retry-After headers

• Posts have character limits enforced by the API
• Some content types (polls, documents) may require additional API features
• HTML markup in post text is not supported

Quick Reference