Get scheduled LinkedIn posts
One page of the account’s SCHEDULED-posts queue: drafts waiting for their publication time, each with post_urn, scheduled_at, text and LinkedIn’s own error_message (wire get-scheduled-posts). A PRIVATE read - nobody on LinkedIn sees it - but it spends the one Content bucket, posting (20/day in series of 3 with a 1200 s pause; free plan 4/day), shared with publishing. Pass author_organization_id (the bare numeric company id) to read a COMPANY PAGE’s queue the account administers instead of the member’s own. Offset-paged: page_size 1-100 (default 20), pass paging.next_cursor back as cursor. rows[].post_urn is the exact handle delete_linkedin_scheduled_post takes. Scheduling itself is not exposed through this API yet - posts are scheduled in LinkedIn’s own UI; this pair reads and cleans the queue.
Contract:
- MCP tool
get_linkedin_scheduled_posts, registry packagemcp.linkedin/linkedin_posting, mountlinkedin.content. - Operation
action, response envelopeaction. - Flags: none.
Authorizations
Access token issued by gtm.service.id. Its access_identity claim carries team_sid, actor_sid and actor_type, and that team scope is authoritative.
Team scope for tokens that do not carry one. Ignored when the token already names a team.
Body
Request body of get_linkedin_scheduled_posts.
LinkedIn account sid (ln_ac_…), the authoring account. Identity-bound: REQUIRED, posts publish AS this account.
18^ln_ac_Rows per page, the node's own [1, 100] gate. Defaults to 20.
1 <= x <= 100The previous page's paging.next_cursor, verbatim. Omit for the first page.
1 - 200Read a company page's queue instead of the member's own: the bare numeric organization id (as in linkedin.com/company/). The account must administer that page or the queue comes back empty.
30^\d+$