linkedin-scraper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_MAX_CALLS_PER_MINUTE | No | Ceiling on calls per rolling minute. 0 turns the ceiling off. | 12 |
| LINKEDIN_MIN_CALL_GAP_SECONDS | No | Minimum quiet gap between the end of one call and the start of the next. Set to 0 (along with LINKEDIN_CALL_GAP_JITTER_SECONDS and LINKEDIN_MAX_CALLS_PER_MINUTE) to switch pacing off entirely. | 3 |
| LINKEDIN_CALL_GAP_JITTER_SECONDS | No | Random extra added to the minimum call gap, so the rhythm is not machine-regular. Set to 0 to switch pacing off entirely along with the other pacing variables. | 1.5 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
send_message and connect_with_person act for the user. Use them only for the exact action, recipient and text the user approved; when the user asks for a draft, or for something these tools cannot do, reply with the text instead. If a write's outcome is unknown, ask the user to check LinkedIn before acting again.
Report what the tools returned, and say when a result may be incomplete.
If LinkedIn waits for a captcha or other verification, ask the user to complete it in the browser, then continue when they say so.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_person_profileC | Get a specific person's LinkedIn profile. |
| search_peopleC | Search for people on LinkedIn. |
| get_my_profileA | Get the authenticated user's own LinkedIn profile. Navigates to /in/me/ and resolves the redirect to obtain the real username before reading the profile, so the url field in the result is the actual profile URL (e.g. linkedin.com/in/johndoe/) rather than /in/me/. |
| get_company_profileC | Get a specific company's LinkedIn profile. |
| get_company_postsC | Get recent posts from a company's LinkedIn feed. |
| search_companiesB | Search for companies on LinkedIn. |
| get_company_employeesA | List employees at a company from the LinkedIn /people/ page, including the demographics aggregate that this view exposes: where employees live, where they studied, and a function breakdown (Engineering, Sales, Operations, etc.). The demographics are unique to this tool. For filtered search by network degree (1st/2nd/3rd) or location, prefer search_people with current_company set to the company URN id. That path also returns more result pages than the /people/ tab. The optional keywords filter narrows results by name, title, or skill. company_name must be the exact LinkedIn URL slug (the path segment after /company/), not the display name. LinkedIn assigns unique slugs and the display name often does not match. For example, the AI lab Anthropic lives at /company/anthropicresearch/, not /company/anthropic/. If you are unsure of the slug, call search_companies first and pick the slug from the returned references. |
| get_job_detailsA | Get job details for a specific job posting on LinkedIn. |
| get_job_apply_urlA | Get how a job posting takes applications, and the employer's application link. Reads the posting without clicking anything. |
| search_jobsA | Search for jobs on LinkedIn. Returns job_ids that can be passed to get_job_details for full info. LinkedIn is moving accounts to a redesigned job search, which keeps only the keywords, date_posted and paging. It drops the filters marked "Classic search only" and reports them in section_errors as filters_dropped. When it drops the location or work type, search again with them in the keywords ("remote python developer in Lyon") and keep doing so; words such as "senior" or "internship" there narrow the results too. Quotes do not make a phrase exact on that search. |
| get_saved_jobsA | List the authenticated user's jobs at one stage of LinkedIn's job tracker. Returns job_ids that can be passed to get_job_details for full info. |
| close_sessionA | Close the current browser session and clean up resources. |
| get_session_statusA | Report local saved-session and serving-process state for requested diagnostics. Reads local observations without opening a browser, starting setup or login, or contacting LinkedIn. Stored files do not prove current authentication. In shared-browser mode these observations belong to the owner, not to a frontend running a login. It answers during browser work without refreshing the browser idle timer. Use ordinary LinkedIn tools directly for their requested work rather than adding a status preflight. |
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 13 tools
Each tool maps to a distinct resource+action pair (person, company, job, session), and the overlapping edges are explicitly disambiguated in descriptions — get_company_employees tells you to prefer search_people for filtered searches, and get_my_profile is clearly separated from get_person_profile. get_job_apply_url vs get_job_details is also cleanly split by concern.
Uniform verb_noun snake_case throughout: get_*, search_*, close_session, get_session_status. No camelCase or stylistic drift.
13 tools covering four resource families (people, companies, jobs, session) is well-scoped, with each tool earning its place. No near-duplicate tools padding the set.
Covers search+detail for people, companies, and jobs plus session teardown and diagnostics, which is the core lifecycle for a scraper. Minor gaps: no session-open/login tool to pair with close_session, and no way to read a person's posts/activity or company job listings beyond the employee demographics view.