LinkedIn API and MCP
Choose a LinkedIn personal profile or company Page and include pageId only for the intended company destination.
Use the connected LinkedIn accountId. Omit pageId for the personal profile. For a company Page, choose pageId from the account's subaccounts.
Fields
pageId
Optional LinkedIn company Page ID. Omit for the personal profile.
For MCP, pass platform-specific fields alongside accountId, platform, text, and mediaUrls. For REST, platform-specific target fields belong inside post.target. Thread content belongs inside post.content.additionalPosts.
Media and formats
Publish text, a single image, a video, or an image carousel. For carousels, Blotato builds a LinkedIn Document from the image URLs. Read the media requirements before submitting a video.
Read LinkedIn media requirements and upload and conversion rules. Public media URLs go directly in mediaUrls. No upload step required.
MCP example
Call blotato_create_post with the following shape. Replace lookup IDs and example media URLs with returned IDs and your media. Adjust the example's settings to the user's request.
{
"accountId": "ACCOUNT_ID_FROM_LOOKUP",
"platform": "linkedin",
"text": "A post for your LinkedIn personal profile.",
"mediaUrls": []
}REST example
Send this JSON to POST https://backend.blotato.com/v2/posts with your blotato-api-key header.
Verify the result
Save the returned
postSubmissionId.If processing continues, use
blotato_get_post_statusorGET /v2/posts/:postSubmissionId.Report the returned status and public URL when supplied.
For scheduling, add scheduledTime or useNextFreeSlot as an MCP argument or a REST top-level sibling of post. See Scheduling and completion rules.
Limits and troubleshooting
Do not add a company Page ID unless the user selects the Page. The example below publishes to the personal profile. LinkedIn analytics availability differs from publishing support. See the analytics guide.
See LinkedIn account guide, platform help, and the Publish Post reference for options and examples.
Last updated