LinkedIn Job Listings

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

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.
• Use it for market-wide role searches: who is hiring RevOps right now, across everyone.

This one is the simplest of the job tools. If you need company size, salary or resume filters, use search_linkedin_job_openings instead — same price.

Use cases

• Find every company hiring a role you sell to. A market-wide keyword search returns the accounts standing up a function right now.
• Track demand for a category. Volume of RevOps or AI-engineer postings over time is a read on where budget is moving.
• Source accounts by geography. Location plus workplace type scopes a list to the territory a rep actually covers.
• Turn listings into contacts. Take the hiring companies and run find_people on their domains for the leader above the open role.

How to use it

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

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

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

Example prompts

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.
• Be specific with the keyword. "Sales" returns everything from SDR to CRO. "RevOps Manager" plus experience_level is a list you can work; a broad keyword is a list you have to re-read.
• Set max_results explicitly. The default of 10 is small for market research, and the call costs the same 0.3 credits at 100.
• Filter at the source. workplace_type and experience_level cut noise before it reaches your client, which is cheaper than filtering the output afterwards.
• Use the enum values as written. experience_level: "mid-senior", workplace_type: "remote" — see Parameters. “Senior-ish” and “WFH” are not values, and a bad one quietly returns nothing.
• Ask for a deduplicated company list. Job boards repeat the same employer many times; you usually want accounts, not rows.
• Ask for the rows as a table. Company, title, location, posted date, job URL — then count reqs per company. Three open reqs at one account is a stronger signal than one req at three.

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.

Parameters

Related tools

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.