Skip to Content
MCPToolsCompany Job Openings

Company Job Openings

Give it one company’s LinkedIn URL or domain, get back that company’s open roles.

Tool
company_job_openings
Cost
0.3 credits
Category
Jobs
Required input
company_linkedin_urlcompany_domain
Returns
Job openings at one company

What it does

  • Retrieves job openings for one company.
  • The only job tool that accepts a company LinkedIn URL. That is the reason to reach for it.
  • Also accepts a domain, and company_job_listings does the same job at the same price — with a domain, either works.
  • Filter with job_title and location.
  • Returns up to 100 openings per call. Default is 10.

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

Use this one when a LinkedIn URL is what you have.


Parameters

ParameterTypeRequiredNotes
company_linkedin_urlstringOne of the twoLinkedIn company page URL
company_domainstringOne of the twoWebsite domain
job_titlearrayNoTitles to include, e.g. ["Account Executive"]
locationstringNoLocation filter
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.

Point it at whichever identifier you hold

Use the LinkedIn company URL if that is what we have on the account. If we only have a website domain, company_job_listings covers the same ground.

Pull openings from the LinkedIn URL

Get the job openings for linkedin.com/company/stripe. Sales titles only, 50 results.

Read the signal

Summarise what those openings say about where they are investing — team, seniority and location.

Example prompts

Ask your clientWhat you get back
”Job openings for linkedin.com/company/stripe”Openings for one company from its LinkedIn page
”Sales openings only, US locations, 50 results”Filtered by job_title and location
”Which teams is this company growing?”Openings grouped by function
”Same thing, but I only have the domain”Route to company_job_listings at the same 0.3 credits

Best prompting practices

  • Name the tool. company_job_listings covers the same scope at the same price, so say which one you want rather than letting the model choose.
  • Filter titles at the source. job_title is free and keeps the response small.
  • Raise max_results. The default of 10 will hide most of a large company’s board.
  • Do not batch it blindly. At 0.3 credits a call, a 100-account list costs 30 credits. Say “stop after 10 and report credits used”.
  • Pair it with headcount. Openings plus head_count_growth_rate tells you whether they are growing or backfilling.

Output

{ "company": "Stripe", "jobs": [ { "title": "Enterprise Account Executive", "location": "New York, NY", "url": "https://linkedin.com/jobs/view/1234567890" } ] }

Credits and limits

0.3 credits per call, flat, whatever max_results you set. Maximum 100 openings per call. Run check_credits (free) before any batch.

All four job tools cost the same, so route by the identifier you hold rather than by price. Send accounts with a domain to company_job_listings and keep this tool for the accounts where only a LinkedIn URL exists — running both on the same company bills twice for one answer.


ToolUse it instead when
company_job_listingsYou have the company name or domain — same scope, same 0.3 credits
linkedin_job_listingsYou want a market-wide keyword search across all companies — 0.3 credits
search_linkedin_job_openingsYou need advanced filters or resume matching — 0.3 credits
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.