linkedin-mcp
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_search_jobsA | Search job listings on LinkedIn. Returns each listing with title, company, location, workplace type, posted salary where the employer provided one, how long ago it was posted, and the job_id. Pass that job_id to linkedin_get_job for the full description rather than re-searching. Results are paged 25 at a time, so a large limit means several page loads. |
| linkedin_get_jobA | Get the full detail for one job posting. Returns the title, company, location, posted age, LinkedIn's job insights (seniority, employment type, headcount) and the complete job description with the "See more" clamp expanded. |
| linkedin_get_profileA | Read a LinkedIn profile. Returns name, headline and location, plus the about text, experience history, education and listed skills unless include_sections is false. Set include_sections to false when you only need to confirm who someone is; it is one page load either way but a much smaller result. |
| linkedin_check_sessionA | Check whether the browser is signed in to LinkedIn. Every other tool needs this to be true; LinkedIn serves a login wall to anonymous visitors on job listings and profiles alike. |
| linkedin_close_sessionA | Disconnect from the browser and free resources. This detaches from Chrome; it leaves the window and the saved session alone. |
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 5 tools
Each tool has a clearly distinct purpose: searching jobs, fetching job details, reading profiles, and managing session state. No overlap between the data-access tools and the session-management tools.
All five tools follow a consistent 'linkedin_<verb>_<noun>' pattern (search_jobs, get_job, get_profile, check_session, close_session). The naming is uniform and predictable.
Five tools is well within the ideal range for a focused server. Every tool contributes to a clear workflow: session management, job search, job details, and profile lookup.
The server covers the core read workflows for LinkedIn jobs and profiles, but lacks profile search or listing capabilities. However, for its stated purpose (searching jobs and reading profiles), the surface is largely complete.