Skip to Content
MCPToolsSearch LinkedIn Jobs

Search LinkedIn Jobs

The advanced job search. Same market as linkedin_job_listings, but with job-function, industry, company, quality and resume-matching filters on top.

Tool
search_linkedin_job_openings
Cost
0.3 credits per job found
Category
Source Leads
Required input
title
Returns
LinkedIn job openings

What it does

  • Searches LinkedIn jobs across all companies, with a large filter set.
  • title is the only required parameter. Everything else narrows the result set.
  • title and locations are arrays, so one call can cover several titles or several cities.
  • Filters go beyond the job itself: job function, industry, company size, organization type, founded year, follower count, whether the poster is a recruiting agency.
  • resume_keywords scores how well each opening matches a resume — the only job tool that does this.

Use this one when you need detailed filtering. For a quick keyword sweep, linkedin_job_listings is simpler to prompt and costs the same.


Use cases

  • Run a precise sweep of a hiring market. Several titles and cities in one call, filtered down to the company profile you sell to.
  • Cut agency noise from a job list. Excluding recruiting agencies is the difference between a list of employers and a list of intermediaries.
  • Catch reqs in the first 24 hours. A tight published_at window puts you in front of the hiring manager before the role fills.
  • Match openings to a candidate or a pitch. resume_keywords scores how closely each opening matches a background, which no other job tool does.
  • Scope by company shape. Size, industry, organization type and founded year keep the results inside your ICP.

How to use it

Connect the MCP server

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

Search with company filters

Search LinkedIn jobs with the titles "RevOps" and "Revenue Operations" in London and Manchester. Companies between 50 and 500 employees, founded after 2020, exclude recruiting agencies, posted in the past week. 50 results.

Add quality filters

Same search, but only openings that publish a salary and have a named recruiter on the post.

Score against a resume

Rerun with resume keywords for Salesforce, HubSpot, SQL and forecasting, then rank the openings by match score.

Example prompts

Ask your clientWhat you get back
”RevOps openings in London posted in the past 24 hours”published_at set to r86400
”Remote AE roles at companies under 200 people, no agencies”work_type, company_size_max, exclude_recruiting_agencies
”Engineering roles only, nothing in accounting or advertising”job_function_include, job_function_exclude
”SaaS and fintech companies only, skip non-profits”industry_include, company_organization_type_exclude
”Only openings at Stripe, Ramp and Mercury”company_include
”Openings with under 10 applicants and Easy Apply”Low-competition list
”Rank these openings against my resume skills”Match scores from resume_keywords

Best prompting practices

  • title is the only required field. Everything else is a filter on top of it — start with the title and add filters one family at a time.
  • Use company_include for account-based searches. Give it a target account list and the search only returns openings at those companies.
  • Prefer industry_include over long title lists. One industry filter usually beats ten near-duplicate titles.
  • Say the time window in words. “Posted in the past week” is enough — your client converts it to r604800. Only write the raw r<seconds> value if you want an exact window.
  • Exclude agencies for outbound. exclude_recruiting_agencies removes the reposted noise that ruins an account list.
  • Turn on enrich_company_data only when you need it. It is slower, and you may already have the firmographics from enrich_organization.
  • Use save_only_unique_items on wide searches. Multiple keywords across multiple cities will return the same opening more than once.
  • Drop the quality filters first when a search comes back empty. require_salary_info, filter_under_10_applicants and require_recruiter_profile each exclude most openings on their own — stacked, they exclude everything.
  • Set max_results and ask for the accounts. Default is 10. “Return 50, deduplicated by company, as a table: company, title, location, posted date, job URL” is the output that becomes a target list.

Output

{ "jobs": [ { "title": "Revenue Operations Lead", "company": "Stripe", "location": "London, United Kingdom", "posted_at": "2026-08-04", "url": "https://linkedin.com/jobs/view/1234567890" } ] }

Credits and limits

0.3 credits per job found, whatever filters you set. max_results accepts 1–100 and defaults to 10, so the default call costs up to 3 credits and a 100-result call up to 30. A search that returns fewer openings than the cap costs less. Run check_credits (free) before a long run of searches.

Stacking filters narrows results fast. If a search returns nothing, drop the quality filters first — require_salary_info and filter_under_10_applicants exclude most openings on their own.


Parameters

Required

ParameterTypeNotes
titlearrayJob title keywords — e.g. ["Software Engineer", "Backend Engineer"]

The optional set is grouped into six families.

ParameterTypeNotes
locationsarrayCities, regions or countries
distancenumberSearch radius around each location. Leave unset for the LinkedIn default
published_atstringr<seconds> window — r86400 past 24h, r604800 past week, r2592000 past month

Job

ParameterTypeNotes
job_typearraypart-time | internship | contract | full-time | temporary
work_typearrayon-site | remote | hybrid
experience_levelarrayentry-level | internship | associate | mid-senior | director
job_function_includearrayJob functions to keep — e.g. ["Engineering", "Analyst"]
job_function_excludearrayJob functions to drop — e.g. ["Accounting / Auditing", "Advertising"]

Company

ParameterTypeNotes
company_includearraySearch only these companies, by name
company_excludearrayCompany names to drop
industry_includearrayCompany industries to keep
industry_excludearrayCompany industries to drop
company_organization_type_includearrayOrganization types to keep — public, private, non-profit, and so on
company_organization_type_excludearrayOrganization types to drop
company_size_minnumberMinimum headcount
company_size_maxnumberMaximum headcount
company_founded_date_minnumberFounded after this year, inclusive
company_founded_date_maxnumberFounded before this year, inclusive
company_followers_count_minnumberMinimum LinkedIn followers
company_followers_count_maxnumberMaximum LinkedIn followers
exclude_recruiting_agenciesbooleanDrop agency-posted roles
enrich_company_databooleanRicher company detail, slower

Quality

ParameterTypeNotes
salary_basestringMinimum base salary, e.g. "60000"
require_salary_infobooleanOnly openings that publish salary
filter_easy_applybooleanOnly Easy Apply openings
filter_under_10_applicantsbooleanOnly openings with fewer than 10 applicants
require_recruiter_profilebooleanOnly openings with a named recruiter

salary_base is under maintenance. LinkedIn publishes salary inconsistently, so treat the filter as best-effort and pair it with require_salary_info rather than relying on it alone.

Matching

ParameterTypeNotes
resume_keywordsarrayArray of {keyword, aliases[]} — scores how well each job matches a resume

Output

ParameterTypeNotes
max_resultsnumber1–100, default 10
save_only_unique_itemsbooleanDrop duplicate openings

ToolUse it instead when
search_job_openingsYou want openings beyond LinkedIn, filtered on the hiring company’s size, revenue and funding — 0.5 per job found
linkedin_job_listingsA plain keyword search is enough — 0.3 per job found
company_job_listingsYou want one company, by name or domain — 0.3 per job found
company_job_openingsYou want one company and only have its LinkedIn URL — 0.3 per job found
job_openings_growth_rateYou want the hiring trend over time, not the openings — 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.