LinkedIn MCP integration for AI agents.
Connect AI agents to LinkedIn through 5 structured actions, including get current member, create article post, and delete post. Review authentication, inputs…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the LinkedIn integration exposes
The LinkedIn Agent App exposes 5 provider-backed actions for social and marketing work. Its current contract lets an authorized agent retrieve the authenticated linkedin member's openid connect profile, create a linkedin article or link post with explicit source url metadata using the posts api, and delete a linkedin post by raw post urn using the posts api. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected LinkedIn account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real LinkedIn capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_memberREADRetrieve the authenticated LinkedIn member's OpenID Connect profile.
create_article_postWRITECreate a LinkedIn article or link post with explicit source URL metadata using the Posts API.
INPUTS: authorUrn / commentary / sourceUrl / title / description
delete_postHIGH IMPACTDelete a LinkedIn post by raw post URN using the Posts API.
INPUTS: postUrn
create_reshareWRITECreate a LinkedIn reshare of an existing post using the Posts API.
INPUTS: authorUrn / parentPostUrn / commentary / visibility / disableReshare
create_text_postWRITECreate a text-only organic LinkedIn post for a member author.
INPUTS: authorUrn / commentary / visibility / disableReshare
INPUT CONTRACTS
Know what the action needs before it runs.
create_article_post
authorUrnREQUIRED- The member author URN, such as urn:li:person:{personId}.
commentaryREQUIRED- The plain text commentary for the post.
sourceUrlREQUIRED- The article or link URL to attach to the post.
titleOPTIONAL- The article title to send to LinkedIn.
descriptionOPTIONAL- The article description to send to LinkedIn.
delete_post
postUrnREQUIRED- The raw LinkedIn post URN, such as urn:li:share:{id}.
create_reshare
authorUrnREQUIRED- The member author URN, such as urn:li:person:{personId}.
parentPostUrnREQUIRED- The raw LinkedIn post URN, such as urn:li:share:{id}.
commentaryOPTIONAL- The plain text commentary for the post.
visibilityOPTIONAL- Who can see the LinkedIn post.
disableReshareOPTIONAL- Whether resharing should be disabled for the new post.
create_text_post
authorUrnREQUIRED- The member author URN, such as urn:li:person:{personId}.
commentaryREQUIRED- The plain text commentary for the post.
visibilityOPTIONAL- Who can see the LinkedIn post.
disableReshareOPTIONAL- Whether resharing should be disabled for the post.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current Member
Retrieve the authenticated LinkedIn member's OpenID Connect profile. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_memberControl Create Article Post
Create a LinkedIn article or link post with explicit source URL metadata using the Posts API. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_article_postVerify with Create Article Post
Create a LinkedIn article or link post with explicit source URL metadata using the Posts API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_article_postSAFETY BOUNDARY
Operate LinkedIn with explicit limits
- Authorize LinkedIn with OAuth 2.0 and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_post` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `w_member_social`, `openid`, `profile`, and `email`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the LinkedIn task completed successfully.
CONNECTION MODEL
OAuth 2.0
LinkedIn uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by LinkedIn.