Linked API
NPM · @LINKEDAPI/MCP · 2 COMPONENTS
Manage LinkedIn messages, connections, posts, and profile data through Linked API.
Available components
Last scanned (8 hours ago)
Scores higher than 43% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 20145 tokens (~296/item across 68 items; 68 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 69 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@linkedapi/mcp@2.3.21
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
accept_invitation ~338
Accepts an incoming connection, company-follow, or newsletter-subscription invitation (st.acceptInvitation action). Set invitationType and provide only its matching URL. If this workflow is still running, do not retry this tool; retrying can queue duplicate accept attempts. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| companyUrl | string | – | Required only for invitationType 'companyFollow'. LinkedIn company page URL. |
| invitationType | string | yes | Invitation type to accept. |
| newsletterUrl | string | – | Required only for invitationType 'newsletterSubscribe'. LinkedIn newsletter URL. |
| personUrl | string | – | Required only for invitationType 'connect'. Public or hashed LinkedIn URL of the person. |
No output schema declared.
No examples provided.
admin_cancel_connection_session ~30
Cancel a pending connection or reconnection session.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | Connection session UUID |
No output schema declared.
No examples provided.
admin_connect_account ~36
Create a connection session to connect a new LinkedIn account. Returns a sessionId and connectionLink that must be opened in a browser.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
admin_create_reconnection_session ~49
Create a reconnection session for an account with status reconnection_required. Returns reconnectionSessionId and reconnectionLink.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | UUID of the account to reconnect |
No output schema declared.
No examples provided.
admin_delete_limits ~65
Delete specific rate limits for an account. Each removed category/period has no limit until set again. Use admin_reset_limits to restore all default limits for the account.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | Account UUID |
| limits | array | yes | Array of limit keys to delete |
No output schema declared.
No examples provided.
admin_disconnect_account ~43
Disconnect a LinkedIn account. This action is irreversible — the account must be reconnected from scratch.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | UUID of the account to disconnect |
No output schema declared.
No examples provided.
admin_get_accounts ~20
Get all connected LinkedIn accounts and pending connection sessions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
admin_get_connection_session ~32
Get connection or reconnection session status by session ID.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | Connection session UUID |
No output schema declared.
No examples provided.
admin_get_limits ~27
Get configured rate limits for an account.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | Account UUID |
No output schema declared.
No examples provided.
admin_get_limits_defaults ~16
Get system default rate limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
admin_get_limits_usage ~31
Get current usage against configured rate limits for an account.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | Account UUID |
No output schema declared.
No examples provided.
admin_get_seats ~38
Get active subscription seats. Each seat allows one connected LinkedIn account. Seat types: core (standard) and plus (includes Sales Navigator).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
admin_get_subscription_status ~22
Get current subscription status, trial eligibility, and cancellation schedule.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
admin_regenerate_token ~37
Regenerate identification token for an account. The old token becomes invalid immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | UUID of the account |
No output schema declared.
No examples provided.
admin_reparse_account_info ~45
Refresh stored profile information for a connected account. Starts a background reparse workflow and returns workflowId.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | UUID of the account to refresh |
No output schema declared.
No examples provided.
admin_reset_limits ~31
Reset all rate limits for an account to the system defaults.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | Account UUID |
No output schema declared.
No examples provided.
admin_set_limits ~101
Set rate limits for an account. Only specified limits are created or updated; other limits remain unchanged. Categories: stPersonProfileViews, stCompanyPageViews, stConnectionRequests, stMessages, stSearchQueries, stReactions, stComments, stPosts, stEndorsements, nvPersonProfileViews, nvCompanyPageViews, nvMessages.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | Account UUID |
| limits | array | yes | Array of limit configurations |
No output schema declared.
No examples provided.
admin_set_seats ~72
Set number of subscription seats. Returns checkout link if no active subscription, otherwise updates immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| billingPeriod | string | yes | Billing period |
| quantity | number | yes | Number of seats (1-1000) |
| seatType | string | yes | Seat type. "plus" unlocks Sales Navigator actions. |
No output schema declared.
No examples provided.
check_connection_status ~268
Allows you to check the connection status between your account and another person (st.checkConnectionStatus action). Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| personUrl | string | yes | Public or hashed LinkedIn URL of the person you want to check the connection status with. (e.g., 'https://www.linkedin.com/in/john-doe') |
No output schema declared.
No examples provided.
comment_on_post ~394
Allows you to leave a comment on a post (st.commentOnPost action); returns the comment's URN and URL. If this workflow is still running, do not retry this tool; retrying can post duplicate comments. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| companyUrl | string | – | LinkedIn company page URL. If specified, the comment will be added on behalf of the company. (e.g., 'https://www.linkedin.com/company/acme-corp') |
| postUrl | string | – | The LinkedIn post URL to comment on (e.g., 'https://www.linkedin.com/posts/username_activity-id') Provide this or postUrn. |
| postUrn | string | – | URN of the post to comment on, as an alternative to postUrl. (e.g., 'urn:li:activity:1234567890123456789') |
| text | string | yes | Comment text, must be up to 1000 characters. |
No output schema declared.
No examples provided.
create_post ~385
Creates a new LinkedIn post with optional mentions and media attachments (st.createPost action). Returns the URL and URN of the new post. If this workflow is still running, do not retry this tool; retrying can create duplicate posts. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | Media attachments for the post. You can add up to 9 images, or 1 video, or 1 document. Cannot mix different attachment types. |
| companyUrl | string | – | LinkedIn company page URL. If specified, the post will be created on the company page (requires admin access). |
| mentions | array | – | People and companies to mention in the text. Each item binds a "@[key]" placeholder to one entity. |
| text | string | yes | Post content, must be up to 3000 characters. Write "@[key]" where a mention should appear and describe that key in mentions. |
No output schema declared.
No examples provided.
create_repost ~448
Reposts a LinkedIn post, either as is or with your own commentary (st.createRepost action). Returns the URL and URN of the repost itself, which is a post of your own account, not of the post that was reshared. Reposting the same post twice from the same account fails with alreadyReposted. If this workflow is still running, do not retry this tool; retrying can create duplicate reposts. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| mentions | array | – | People and companies to mention in the commentary. Each item binds a "@[key]" placeholder to one entity. |
| postUrl | string | – | LinkedIn URL of the post to repost. (e.g., 'https://www.linkedin.com/posts/username_activity-id') Provide this or postUrn. |
| postUrn | string | – | URN of the post to repost, as an alternative to postUrl. (e.g., 'urn:li:activity:1234567890123456789') |
| text | string | – | Your own commentary, up to 3000 characters. Without it the post is reposted as is. Write "@[key]" where a mention should appear and describe that key in mentions. |
No output schema declared.
No examples provided.
endorse_person_skill ~372
Endorses one skill by name on a 1st-degree connection's profile. Skill names are in the profile owner's language, regardless of your LinkedIn language. An already-endorsed skill counts as success and is never removed. Every success, including an existing endorsement, counts toward the stEndorsements limit. Use endorse_person_skills to select skills with patterns or endorse all skills. If this workflow is still running, do not retry this tool; retrying can count the same skill toward the stEndorsements limit again. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| personUrl | string | yes | Public or hashed LinkedIn URL of your 1st-degree connection. |
| skillName | string | yes | Exact skill name in the profile owner's language, up to 200 characters. Letter case and extra spaces are ignored. This is not a pattern. |
No output schema declared.
No examples provided.
endorse_person_skills ~470
Endorses selected skills of a 1st-degree connection, returning each selected skill's name, success and error if it failed. Skill names are in the profile owner's language. Patterns use RE2, are case-insensitive and match anywhere; anchor with ^…$ to match a whole name. Omit skillNamePatterns to endorse all skills; never pass []. An already-endorsed skill counts as success and is never removed. Each success counts toward the stEndorsements limit, including existing endorsements. The limit is checked for each skill; a failure does not stop the others, so check every item's success. If this workflow is still running, do not retry this tool; retrying can count the same skills toward the stEndorsements limit again. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| personUrl | string | yes | Public or hashed LinkedIn URL of your 1st-degree connection. |
| skillNamePatterns | array | – | Optional. 1-20 RE2 patterns, each 1-200 characters, matching names in the profile owner's language. Any matching pattern selects the skill. Matching is case-insensitive and searches anywhere: manage… |
No output schema declared.
No examples provided.
execute_custom_workflow ~295
Execute a custom workflow definition. Pass a single action with actionType and its parameters at the top level. A single-action or array definition can alternatively be passed in definition. If this workflow is still running, do not retry this tool; retrying can duplicate any write actions inside the custom workflow. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| actionType | string | – | The action type for a single-action workflow. |
| definition | – | – | A single-action or array workflow definition. |
No output schema declared.
No examples provided.
fetch_company ~478
Allows you to open a company page to retrieve its basic information (st.openCompanyPage action). Can optionally retrieve employees, posts and decision makers. The basic information carries urn — the permanent LinkedIn organization URN of the company (urn:li:organization:<id>); retrieved employees and decision makers carry their own member urn (urn:li:member:<id>), and retrieved posts carry urn on their author and reposter. Each of them is null when LinkedIn does not expose the identifier. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| companyUrl | string | yes | Public or hashed LinkedIn URL of the company. (e.g., 'https://www.linkedin.com/company/microsoft') |
| dmsRetrievalConfig | object | – | Optional. Configuration for retrieving decision makers. Available only if retrieveDMs is true. |
| employeesRetrievalConfig | object | – | Optional. Configuration for retrieving employees. Available only if retrieveEmployees is true. |
| postsRetrievalConfig | object | – | Optional. Configuration for retrieving posts. Available only if retrievePosts is true. |
| retrieveDMs | boolean | – | Optional. Whether to retrieve the company's decision makers information. Default is false. |
| retrieveEmployees | boolean | – | Optional. Whether to retrieve the company's employees information. Default is false. |
| retrievePosts | boolean | – | Optional. Whether to retrieve the company's posts information. Default is false. |
No output schema declared.
No examples provided.
fetch_job ~300
Open a LinkedIn job and retrieve its details such as company, location, salary, and description (st.openJob action). The result carries urn — the permanent LinkedIn job posting URN (urn:li:jobPosting:<jobId>) — which is null when LinkedIn does not expose the identifier. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| jobUrl | string | yes | LinkedIn URL of the job. (e.g., 'https://www.linkedin.com/jobs/view/4416248954/') |
No output schema declared.
No examples provided.
fetch_person ~617
Allows you to open a person page to retrieve their basic information and perform additional person-related actions if needed. (st.openPersonPage action). Allows additional optional retrieval of experience, education, skills, languages, posts, comments and reactions. The basic information carries urn — the person's permanent LinkedIn member URN (urn:li:member:<id>), or null when LinkedIn does not expose it. Retrieved posts carry urn on their author and reposter as well. ⚠️ **PERFORMANCE WARNING**: Only set additional retrieval flags to true if you specifically need that data. Each additional parameter significantly increases execution time: 💡 **Recommendation**: Start with basic info only. Only request additional data if the user explicitly asks for it or if it's essential for the current task. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| commentsRetrievalConfig | object | – | Optional. Configuration for retrieving comments. Available only if retrieveComments is true. |
| personUrl | string | yes | The LinkedIn profile URL of the person to fetch (e.g., 'https://www.linkedin.com/in/john-doe') |
| postsRetrievalConfig | object | – | Optional. Configuration for retrieving posts. Available only if retrievePosts is true. |
| reactionsRetrievalConfig | object | – | Optional. Configuration for retrieving reactions. Available only if retrieveReactions is true. |
| retrieveComments | boolean | – | Optional. Whether to retrieve the person's comments information. Default is false. |
| retrieveEducation | boolean | – | Optional. Whether to retrieve the person's education information. Default is false. |
| retrieveExperience | boolean | – | Optional. Whether to retrieve the person's experience information. Default is false. |
| retrieveLanguages | boolean | – | Optional. Whether to retrieve the person's languages information. Default is false. |
| retrievePosts | boolean | – | Optional. Whether to retrieve the person's posts information. Default is false. |
| retrieveReactions | boolean | – | Optional. Whether to retrieve the person's reactions information. Default is false. |
| retrieveSkills | boolean | – | Optional. Whether to retrieve the person's skills information. Default is false. |
No output schema declared.
No examples provided.
fetch_post ~542
Open a LinkedIn post and retrieve its data, with optional comments and reactions. (st.openPost action). The author and reposter carry urn — a member URN (urn:li:member:<id>) for a person actor and an organization URN (urn:li:organization:<id>) for a company actor — and each retrieved reaction carries an actor object (type, name, urn, profileUrl or companyUrl, headline, and viewerState.connectionDegree for a person) with the same urn identity; each urn is null when LinkedIn does not expose the identifier. This action reads identifiers from the post page itself, so it resolves actor URNs that post listings such as retrieve_feed cannot. Comment authors carry no URN. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| commentsRetrievalConfig | object | – | Optional. Applies only when retrieveComments is true. Controls comments retrieval (limit, replies, sort). |
| postUrl | string | – | LinkedIn URL of the post. (e.g., 'https://www.linkedin.com/posts/username_activity-id') Provide this or postUrn. |
| postUrn | string | – | URN of the post to fetch, as an alternative to postUrl. (e.g., 'urn:li:activity:1234567890123456789') |
| reactionsRetrievalConfig | object | – | Optional. Applies only when retrieveReactions is true. Controls reactions retrieval (limit). |
| retrieveComments | boolean | – | Optional. When true, also retrieve comments for the post. Configure via commentsRetrievalConfig. |
| retrieveReactions | boolean | – | Optional. When true, also retrieve reactions for the post. Configure via reactionsRetrievalConfig. |
No output schema declared.
No examples provided.
get_api_usage ~98
Retrieve Linked API usage statistics. Date range must not exceed 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | End date for the statistics period in ISO 8601 format (e.g., '2024-01-30T00:00:00Z') |
| start | string | yes | Start date for the statistics period in ISO 8601 format (e.g., '2024-01-01T00:00:00Z') |
No output schema declared.
No examples provided.
get_changelog ~228
Read the public Linked API changelog: what was released and when, newest first. Use it when the user asks what is new or recently changed in Linked API, or whether Linked API supports something yet — a capability may have shipped recently, so check here before saying it does not exist. Each release has a date and items with a title, a body and docs, a path on https://linkedapi.io (prefix it to link the user to the documentation). Needs no Linked API tokens and does not start a LinkedIn workflow. The same changelog is published at https://linkedapi.io/changelog.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Only return releases for the week containing this point and later: an ISO 8601 date (e.g. '2026-10-01') or an instant with a time zone (e.g. '2026-10-01T00:00:00Z'). A release covers a week and is da… |
No output schema declared.
No examples provided.
get_conversation ~470
Legacy. Prefer get_inbox with personUrl. Retrieve a conversation with a LinkedIn person via standard LinkedIn messaging. Returns the conversation immediately if it has already been synced. If the conversation has not been synced yet, this tool starts a syncConversation workflow and returns its ack ({status, workflowId, operationName: "syncConversation", message}); the client should call get_workflow_result with that workflowId until completion, then call get_conversation again to read the synced messages. The result carries syncUntil — the moment syncing of this conversation stops. Once it is in the past the messages are still returned but no longer updated; call sync_conversation again for the same person to resume updates. It also carries personUrn — the permanent LinkedIn member URN (urn:li:member:<id>) of the person, or null when LinkedIn does not expose it. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| personUrl | string | yes | The LinkedIn URL of the person whose conversation you want to poll (e.g., 'https://www.linkedin.com/in/john-doe') |
| since | string | – | Optional ISO 8601 timestamp to only retrieve messages since this date (e.g., '2024-01-15T10:30:00Z'). If not provided, the entire conversation history will be returned. |
No output schema declared.
No examples provided.
get_inbox ~619
Default way to read LinkedIn messages (standard and Sales Navigator), newest first. Without personUrl returns new messages across all conversations since inbox monitoring was enabled; requires sync_inbox (or nv_sync_inbox) once per account. With personUrl returns the whole known conversation with that person, including history loaded by sync_conversation, as { messages, threads }: each message also carries inboxMessageId (its id in the result without personUrl, or null) and threadId may be null; each thread carries historyFrom and historyComplete. Check threads[].historyComplete – if false and you need earlier messages, call sync_conversation once, then call get_inbox again. Every message carries personUrn — the permanent LinkedIn member URN (urn:li:member:<id>) of the person on the other side of the thread, or null when LinkedIn does not expose it. personHashedUrl is LinkedIn's hashed profile URL and is always present; personPublicUrl is the public vanity URL when that person has been resolved, otherwise null. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the…
| Name | Type | Req | Description |
|---|---|---|---|
| personUrl | string | – | Optional LinkedIn URL of one person to get the whole known conversation with them instead of the whole inbox (e.g., 'https://www.linkedin.com/in/john-doe'). A hashed URL (personHashedUrl from a messa… |
| since | string | – | Optional ISO 8601 timestamp to only retrieve messages at or after this date (e.g., '2024-01-15T10:30:00Z'). If not provided, all captured messages are returned. Message times are whole minutes. |
| threadId | string | – | Optional conversation thread identifier to restrict the result to a single thread. |
| type | string | – | Optional inbox type filter: "st" for standard messages, "nv" for Sales Navigator messages. If omitted, both are returned. |
No output schema declared.
No examples provided.
get_network ~403
Get connection events from the monitored network, newest first. Requires network monitoring to be enabled once with sync_network. Event types: "connectionAccepted" (a connection request you sent was accepted), "connectionAdded" (a new connection appeared in your network), "connectionRequestReceived" (someone sent you a connection request). Every event carries personUrn — the permanent LinkedIn member URN (urn:li:member:<id>) of the person the event is about, or null when LinkedIn does not expose it or the event was recorded before URNs were captured. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Optional ISO 8601 timestamp to only retrieve events after this date (e.g., '2024-01-15T10:30:00Z'). If not provided, all captured events are returned. |
| type | string | – | Optional event type filter: "connectionAccepted", "connectionAdded", or "connectionRequestReceived". If omitted, all event types are returned. |
No output schema declared.
No examples provided.
get_workflow_result ~249
Check the current state of a previously started Linked API workflow. Returns the final result when the workflow has completed, otherwise returns the current in-progress snapshot ({status, pendingReason, workflowId, operationName, message}). The server long-polls up to waitSeconds while the workflow is still running; if the budget elapses without completion, the in-progress snapshot is returned and the client should call this tool again with the same workflowId and operationName. Exception: when pendingReason is "outsideWorkingHours" the workflow is parked until the account working hours reopen — the server returns immediately without polling, message states when that is, and calling this tool again before then will report the same state.
| Name | Type | Req | Description |
|---|---|---|---|
| operationName | string | yes | Required. The operationName returned by the original Linked API tool call. Used to map the response to the right operation. |
| waitSeconds | number | – | Optional. Maximum seconds the server should wait for the workflow to complete before returning the current in-progress snapshot. Defaults to the maximum the current MCP client allows; pass 0 to get a… |
| workflowId | string | yes | Required. The workflow ID returned by the original Linked API tool call. |
No output schema declared.
No examples provided.
ignore_invitation ~339
Ignores an incoming connection, company-follow, or newsletter-subscription invitation (st.ignoreInvitation action). Set invitationType and provide only its matching URL. If this workflow is still running, do not retry this tool; retrying can queue duplicate ignore attempts. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| companyUrl | string | – | Required only for invitationType 'companyFollow'. LinkedIn company page URL. |
| invitationType | string | yes | Invitation type to ignore. |
| newsletterUrl | string | – | Required only for invitationType 'newsletterSubscribe'. LinkedIn newsletter URL. |
| personUrl | string | – | Required only for invitationType 'connect'. Public or hashed LinkedIn URL of the person. |
No output schema declared.
No examples provided.
manage_conversation ~273
Archive, star, or mute a conversation thread by threadId (st.manageConversation action). Provide the threadId as returned by get_inbox and the operation to perform. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | Operation to perform on the conversation thread. |
| threadId | string | yes | Conversation thread identifier, as returned by get_inbox. |
No output schema declared.
No examples provided.
nv_fetch_company ~409
Allows you to open a company page in Sales Navigator to retrieve its basic information (nv.openCompanyPage action). Can optionally retrieve employees and decision makers. The basic information carries urn — the permanent LinkedIn organization URN of the company (urn:li:organization:<id>) — and retrieved employees and decision makers carry their own member urn (urn:li:member:<id>); each is null when LinkedIn does not expose the identifier. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| companyHashedUrl | string | yes | Hashed LinkedIn URL of the company. |
| dmsRetrievalConfig | object | – | Optional. Configuration for retrieving decision makers. Available only if retrieveDMs is true. |
| employeesRetrievalConfig | object | – | Optional. Configuration for retrieving employees. Available only if retrieveEmployees is true. |
| retrieveDMs | boolean | – | Optional. Whether to retrieve the company's decision makers information. Default is false. |
| retrieveEmployees | boolean | – | Optional. Whether to retrieve the company's employees information. Default is false. |
No output schema declared.
No examples provided.
nv_fetch_person ~324
Allows you to open a person page in Sales Navigator to retrieve their basic information (nv.openPersonPage action). The result carries urn — the person's permanent LinkedIn member URN (urn:li:member:<id>) — and companyUrn for their current company (urn:li:organization:<id>); either is null when LinkedIn does not expose it. The same person carries the same urn in standard interface results, so it can be used to match Sales Navigator results against them. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| personHashedUrl | string | yes | Hashed LinkedIn URL of the person. |
No output schema declared.
No examples provided.
nv_get_conversation ~430
Legacy. Prefer get_inbox with personUrl. Retrieve a conversation with a LinkedIn person via Sales Navigator messaging. Returns the conversation immediately if it has already been synced. If the conversation has not been synced yet, this tool starts an nvSyncConversation workflow and returns its ack ({status, workflowId, operationName: "nvSyncConversation", message}); the client should call get_workflow_result with that workflowId until completion, then call nv_get_conversation again to read the synced messages. The result carries personUrn — the permanent LinkedIn member URN (urn:li:member:<id>) of the person, or null when LinkedIn does not expose it. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| personUrl | string | yes | The LinkedIn URL of the person whose conversation you want to poll (e.g., 'https://www.linkedin.com/in/john-doe') |
| since | string | – | Optional ISO 8601 timestamp to only retrieve messages since this date (e.g., '2024-01-15T10:30:00Z'). If not provided, the entire conversation history will be returned. |
No output schema declared.
No examples provided.
nv_manage_conversation ~276
Archive or unarchive a Sales Navigator conversation thread by threadId (nv.manageConversation action). Provide the threadId as returned by get_inbox and the operation to perform. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | Operation to perform on the Sales Navigator conversation thread. |
| threadId | string | yes | Conversation thread identifier, as returned by get_inbox. |
No output schema declared.
No examples provided.
nv_search_companies ~336
Allows you to search for companies in Sales Navigator applying various filtering criteria. (nv.searchCompanies action). Every company in the result carries urn — its permanent LinkedIn organization URN (urn:li:organization:<id>), or null when LinkedIn does not expose it. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Optional. Object that specifies filtering criteria for companies. When multiple filter fields are specified, they are combined using AND logic. |
| limit | number | – | Optional. Number of search results to return. Defaults to 25, with a maximum value of 1000. |
| term | string | – | Optional. Keyword or phrase to search. |
No output schema declared.
No examples provided.
nv_search_people ~394
Allows you to search people in Sales Navigator applying various filtering criteria. (nv.searchPeople action). Every person in the result carries urn — their permanent LinkedIn member URN (urn:li:member:<id>), or null when LinkedIn does not expose it. The same person carries the same urn in standard interface results, so it can be used to match Sales Navigator results against them. Every person also carries viewerState.connectionDegree — your connection degree to them (1st, 2nd, 3rd+), or null when LinkedIn shows none. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Optional. Object that specifies filtering criteria for people. When multiple filter fields are specified, they are combined using AND logic. |
| limit | number | – | Optional. Number of search results to return. Defaults to 25, with a maximum value of 2500. |
| term | string | – | Optional. Keyword or phrase to search. |
No output schema declared.
No examples provided.
nv_send_message ~404
Allows you to send a message to a person in Sales Navigator (nv.sendMessage action). Provide either personUrl or threadId (threadId replies into an existing conversation thread and takes precedence). If this workflow is still running, do not retry this tool; retrying can send duplicate Sales Navigator messages to the same person. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| personUrl | string | – | LinkedIn URL of the person you want to send a message to (e.g., 'https://www.linkedin.com/in/john-doe'). Optional if threadId is provided. |
| subject | string | – | Subject line, must be up to 80 characters. Required when starting a new conversation; ignored when replying into an existing thread via threadId. |
| text | string | yes | The message text, must be up to 1900 characters. |
| threadId | string | – | Optional conversation thread identifier to reply into, as returned by get_inbox. Provide this instead of personUrl to reply directly into a known thread. |
No output schema declared.
No examples provided.
nv_sync_conversation ~379
Loads this person's earlier Sales Navigator message history (nv.syncConversation action). Call once per person. Do not call it to check for new messages – use get_inbox. After it completes, read the history with get_inbox and personUrl. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Syncing period, not the depth of history: how many days new messages keep being added to the loaded history, from 1 to 90. Defaults to 30. The whole conversation is read regardless. Counted from the… |
| personUrl | string | yes | The LinkedIn URL of the person whose Sales Navigator message history you want to load (e.g., 'https://www.linkedin.com/in/john-doe') |
No output schema declared.
No examples provided.
nv_sync_inbox ~269
Recommended first step before reading Sales Navigator messages. Enable whole-inbox monitoring in Sales Navigator so every incoming conversation can be polled with get_inbox (nv.syncInbox action). Run once per account, before sending messages whose replies you want to read; only messages that arrive after it is enabled are captured. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
react_to_comment ~284
React to a comment by commentUrl (like, love, support, celebrate, insightful, funny). If this workflow is still running, do not retry this tool; retrying can queue duplicate reaction attempts. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| commentUrl | string | yes | LinkedIn URL of the comment to react to. |
| type | string | – | Optional. Enum describing the reaction type. Defaults to "like". |
No output schema declared.
No examples provided.
react_to_post ~384
Allows you to react to a post using any available reaction type (st.reactToPost action). If this workflow is still running, do not retry this tool; retrying can queue duplicate reaction attempts. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| companyUrl | string | – | LinkedIn company page URL. If specified, the reaction will be added on behalf of the company. (e.g., 'https://www.linkedin.com/company/acme-corp') |
| postUrl | string | – | LinkedIn URL of the post to react. (e.g., 'https://www.linkedin.com/posts/username_activity-id') Provide this or postUrn. |
| postUrn | string | – | URN of the post to react to, as an alternative to postUrl. (e.g., 'urn:li:activity:1234567890123456789') |
| type | string | yes | Enum describing the reaction type. |
No output schema declared.
No examples provided.
remove_connection ~286
Allows you to remove a person from your connections (st.removeConnection action). If this workflow is still running, do not retry this tool; retrying can queue duplicate removal attempts for the same person. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| personUrl | string | yes | Public or hashed LinkedIn URL of the person you want to remove from your connections. (e.g., 'https://www.linkedin.com/in/john-doe') |
No output schema declared.
No examples provided.
reply_to_comment ~279
Reply to a comment by commentUrl; returns the reply's URN and URL. If this workflow is still running, do not retry this tool; retrying can post duplicate replies. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work. A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.
| Name | Type | Req | Description |
|---|---|---|---|
| commentUrl | string | yes | LinkedIn URL of the comment to reply to. |
| text | string | yes | Reply text, must be up to 1000 characters. |
No output schema declared.
No examples provided.
How do I install the Linked API MCP server?
Linked API runs locally as an npm package, launched with npx -y @linkedapi/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @linkedapi/mcp
claude mcp add linked-api-linkedapi-mcp -- npx -y @linkedapi/mcp
What is the Linked API MCP server?
Linked API is an MCP server listed in the public MCP registry as io.github.Linked-API/linkedapi-mcp. Manage LinkedIn messages, connections, posts, and profile data through Linked API. This page covers its npm package (@linkedapi/mcp).
Is the Linked API MCP server safe to use?
Linked API scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Linked API MCP server expose?
Linked API exposes 68 tools: send_message, sync_inbox, get_inbox, sync_conversation, get_conversation, and 63 more. Their descriptions and schemas cost roughly 18,924 tokens of context every time the server is loaded.
Is the Linked API MCP server still maintained?
Linked API is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Linked API MCP server under?
Linked API declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.