Company Job Openings

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

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.

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

Use cases

• Work from a LinkedIn URL you already have. This is the only job tool that takes a company LinkedIn page, so it fits lists sourced from LinkedIn rather than from domains.
• Check hiring on an account mid-conversation. One call confirms whether the team you are selling into is growing before you send the follow-up.
• Map which functions are expanding. Group openings by title to see whether the money is going to sales, engineering or support this quarter.
• Enrich a signal list. Attach current openings to accounts you have already qualified so the outreach can name a specific role they are hiring for.

How to use it

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.

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

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

Example prompts

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.
• Route by the identifier you hold. This tool takes company_linkedin_url; the other takes the domain. Tell your client which column your list actually has, or it will call both on the same account and bill twice for one answer.
• Filter titles at the source, in array form. job_title: ["Account Executive"] is free and keeps the response small.
• There is no title exclusion here. job_title_exclude only exists on company_job_listings. If dropping roles matters more than accepting a LinkedIn URL, resolve the domain and use that tool instead.
• Raise max_results. The default of 10 will hide most of a large company’s board. It goes to 100 for the same 0.3 credits.
• Ask for the raw rows. “Return a table: title, location, posted date, URL” — a prose summary of a hiring board is not something you can sort or sequence from.
• 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.

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.