LinkedIn MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| authenticate_linkedinA | Authenticate with LinkedIn OAuth - works with standard LinkedIn Developer Application |
| revoke_linkedin_authA | Revoke LinkedIn authentication and clear stored tokens |
| get_my_profileA | Get my LinkedIn profile information using OpenID Connect - works with standard OAuth scopes |
| get_company_infoC | Get basic company information - limited access, may require Marketing Solutions partnership in future |
| get_company_profileC | Get detailed company profile information - limited access, may require Marketing Solutions partnership in future |
| update_partnershipsA | Update LinkedIn API partnership access settings when you get approved for special access |
| create_postB | Create a LinkedIn post with text content and visibility settings |
| get_my_postsA | Retrieve your published LinkedIn posts with engagement metrics |
| get_feedB | Access your LinkedIn feed with posts from your network |
| like_postC | Like a LinkedIn post to show appreciation |
| comment_on_postA | Add a thoughtful comment to a LinkedIn post |
| share_postC | Share a LinkedIn post with optional commentary |
| search_jobsB | Search LinkedIn jobs with advanced filters and criteria |
| get_jobB | Get comprehensive details about a specific LinkedIn job posting |
| save_jobA | Bookmark a job for later review and application |
| get_saved_jobsA | Retrieve all your saved and bookmarked job listings |
| get_job_applicationsB | Track status and details of your job applications |
| search_peopleC | Search LinkedIn professionals with advanced filters and criteria |
| get_profileB | Access detailed LinkedIn profile information for any user |
| get_connectionsB | Retrieve your complete LinkedIn connections list |
| send_connection_requestB | Send personalized connection requests to LinkedIn users |
| get_connection_requestsB | View and manage pending incoming connection requests |
| accept_connection_requestA | Accept incoming connection requests to grow your network |
| get_conversationsA | Access your LinkedIn conversation threads and chat history |
| get_messagesB | Retrieve messages from a specific conversation thread |
| send_messageA | Send direct messages to your LinkedIn connections |
| get_profile_analyticsC | Access comprehensive profile performance and engagement metrics |
| get_post_analyticsB | Get detailed analytics and engagement data for your posts |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 28 tools
Most tools have distinct purposes, but there is slight overlap between get_my_profile and get_profile, and between get_company_info and get_company_profile. These are minor and descriptions help.
All tools use a consistent snake_case verb_noun pattern (e.g., accept_connection_request, search_jobs). No mixed conventions or unclear names.
At 28 tools, the count exceeds the 25+ threshold for 'too many' per the rubric. While each tool has a clear role, the server would benefit from consolidation or pruning.
Covers many core LinkedIn actions (search, post, message, connect), but lacks update/delete for posts, profile editing, and connection management beyond accept. Notable gaps for a full-lifecycle tool.