Search LinkedIn jobs

Search LinkedIn jobs

Returns public LinkedIn job listings by keyword, location, seniority and job type, or for given job URLs, with title, company, salary, description and apply link.

Note: maxJobs (default 25, up to 500) caps each search. jobType, experienceLevel and remote are applied after fetching, and jobs they skip are not charged. Billed per job returned.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "alphaosint": { "url": "https://mcp.apify.com/?tools=johnvc/linkedin-profile-api,johnvc/linkedin-company-api,johnvc/linkedin-people-search-api,johnvc/linkedin-company-employees-api,johnvc/crunchbase-company-api,johnvc/google-maps-places-api,johnvc/Google-Jobs-Scraper,johnvc/linkedin-jobs-api" } } }

Call the MCP tool johnvc--linkedin-jobs-api.

Server URL: https://mcp.apify.com/?tools=johnvc/linkedin-profile-api,johnvc/linkedin-company-api,johnvc/linkedin-people-search-api,johnvc/linkedin-company-employees-api,johnvc/crunchbase-company-api,johnvc/google-maps-places-api,johnvc/Google-Jobs-Scraper,johnvc/linkedin-jobs-api

Note: Apify's hosted MCP server; the URL loads one tool per listed source, named like johnvc--linkedin-profile-api. Sign in to Apify in the browser, or send an Apify token as a Bearer header. A tool waits up to 45 seconds; for longer runs, poll get-actor-run, then get-dataset-items.

API (official)

• Base URL: https://api.apify.com/v2
• Endpoint: POST /acts/johnvc~linkedin-jobs-api/run-sync-get-dataset-items
• Auth: send the header Authorization: Bearer $APIFY_TOKEN
• Get a key: https://console.apify.com/settings/integrations
• Docs: https://docs.apify.com/api/v2/actor-run-sync-get-dataset-items-post

Note: Each source is an Apify Actor: POST its JSON input and the response holds the result rows. A run longer than 300 seconds returns 408; start a long run with the Actor's /runs endpoint instead and read its dataset. Runs bill to the Apify account.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.