Skip to Content
MCPToolsLinkedIn Job Listings

LinkedIn Job Listings

Give it a keyword, get back matching LinkedIn job posts from across the whole market.

Tool
linkedin_job_listings
Cost
0.3 credits
Category
Jobs
Required input
keywords
Returns
LinkedIn job listings

What it does

  • Searches LinkedIn jobs across all companies by keyword and location.
  • keywords is a single string, not an array — "RevOps", "Head of Sales".
  • Narrow the result set with location, employment_type, experience_level and workplace_type.
  • Returns up to 100 listings per call. Default is 10.
  • Use it for market-wide role searches: who is hiring RevOps right now, across everyone.

There are four job tools. All four cost 0.3 credits, so pick by scope and input:

ToolScopeCost
linkedin_job_listingsAll companies, plain keyword search0.3 credits
search_linkedin_job_openingsAll companies, advanced filters and resume matching0.3 credits
company_job_listingsOne company, by name or domain0.3 credits
company_job_openingsOne company, by LinkedIn URL or domain0.3 credits

This one is the simplest of the four. If you need company size, salary or resume filters, use search_linkedin_job_openings instead.


Parameters

ParameterTypeRequiredNotes
keywordsstringYesRole or skill keyword, e.g. "RevOps"
locationstringNoCity, region or country
employment_typestringNofull-time | part-time | internship | contract | temporary
experience_levelstringNointernship | associate | entry | director | mid-senior | executive
workplace_typestringNoremote | hybrid | office
max_resultsnumberNo1–100, default 10

How to use it

Connect the MCP server

Follow the setup guide for your client. Browser sign-in, no API key.

Find LinkedIn job listings for "RevOps" in the United Kingdom. Remote only, mid-senior level. Return 50 results.

Turn listings into an account list

From those listings, give me the unique hiring companies with a count of open roles each. Sort by role count.

Find the people behind the hiring

For the top 10 hiring companies, find the VP Sales and Head of RevOps.

Example prompts

Ask your clientWhat you get back
”LinkedIn job listings for RevOps in London”Matching job posts with company and location
”Who is hiring remote SDRs right now, 50 results”Market-wide listings filtered to remote
”Contract data engineer roles, entry level”Listings filtered by employment type and seniority
”Companies hiring RevOps, then find their VP Sales”Chains find_people_within_company after the search

Best prompting practices

  • Keep keywords to one phrase. It is a string, not a list. Run separate calls for separate roles.
  • Name the scope. Say “across all companies” so your client does not reach for a one-company tool.
  • Set max_results explicitly. The default of 10 is small for market research.
  • Filter at the source. workplace_type and experience_level cut noise before it reaches your client, which is cheaper than filtering the output afterwards.
  • Ask for a deduplicated company list. Job boards repeat the same employer many times; you usually want accounts, not rows.

Output

{ "jobs": [ { "title": "RevOps Manager", "company": "Stripe", "location": "London, United Kingdom", "url": "https://linkedin.com/jobs/view/1234567890" } ] }

Credits and limits

0.3 credits per call, flat, whatever max_results you set. Maximum 100 listings per call. Run check_credits (free) before a long run of searches.

Hiring keywords are noisy. "Sales" returns everything from SDR to Chief Revenue Officer. Use a specific title plus experience_level to keep the list usable.


ToolUse it instead when
search_linkedin_job_openingsYou need company, salary or resume-match filters — 0.3 credits
company_job_listingsYou want the open roles at one named company — 0.3 credits
company_job_openingsYou only have the company’s LinkedIn URL — 0.3 credits
job_openings_growth_rateYou want the hiring trend over time, not the listings — 3 credits

Next steps

  • All MCP tools — the full catalogue with credit costs
  • Signals & ABM — workflows that turn hiring signals into an account list

Keep learning

Two courses take these tools past the reference page — clustered by GTM job, then chained into workflows.