Company Job Listings

Give it one company name or domain, get back that company’s job listings.

What it does

• Searches job listings at one company, identified by name or website domain.
• Does not accept a LinkedIn company URL. Pass a domain instead, or use company_job_openings if the URL is all you have.
• Filter with job_title and job_location, or cut noise with job_title_exclude and job_location_exclude.
• company_domain is the more reliable of the two inputs — names collide, domains do not.

Both single-company tools cost the same. Reach for company_job_openings when you have a LinkedIn URL and no domain.

Use cases

• Qualify a single account’s hiring intent. Open roles show where a company is investing right now, which is a better buying signal than headcount alone.
• Read the stack from the job description. Roles that name the tools they want you to know reveal the tech stack without a separate technographic call.
• Watch a target account on a schedule. Re-run the same domain monthly and the delta tells you which teams are being built out.
• Route to the right buyer. Sales roles point at a sales leader, engineering roles at a CTO — the listings tell you which door to knock on.

How to use it

List the open roles at stripe.com. Limit 50.

Same company, only sales and revenue operations titles. Exclude anything
with "intern" in the title.

For each of these 20 domains, list open sales roles. Use the domain, not
the company name. Report credits used.

Example prompts

Best prompting practices

• Pass the domain. “Apex” matches a dozen companies; apex.com matches one.
• Say “do not use a LinkedIn URL”. If your client has a LinkedIn page in context it may route to company_job_openings by mistake — same price, but a second call for the same answer.
• Filter titles at the source, in array form. job_title: ["Account Executive", "Enterprise AE"]. “Sales roles” is a description, not a filter, and anything you leave unsaid was not applied.
• State the exclusions too. job_title_exclude and job_location_exclude are free and drop the roles and regions you never sell to before they are returned — cheaper than filtering the response by hand.
• Raise limit. The default of 5 will hide most of a mid-size company’s board. It goes to 50, and the call costs the same 0.3 credits either way.
• Ask for the raw rows. “Return a table: job title, location, posted date, job URL.” Left alone your client reports “they’re hiring in sales” and you lose the posting date that made it a timing signal.
• Number the steps over a target list. Step 1 the domains, step 2 company_job_listings per domain, step 3 keep only accounts with a matching role open. Put the stop point before step 2.
• Cap the batch. “Stop after 20 companies and report credits used” keeps a target list from running away with your balance.

Output

{
  "company": "Stripe",
  "jobs": [
    {
      "title": "Account Executive",
      "location": "London, United Kingdom",
      "url": "https://stripe.com/jobs/listing/1234567890"
    }
  ]
}

Credits and limits

0.3 credits per call, flat, whatever limit you set. Maximum 50 listings per call. Run check_credits (free) before scoring a large target list.

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.