Company Job Listings
/company-job-listingsReturns the open roles at one company by name or domain, with job title, location and listing URL, for a flat 1.5 credits per call.
Overview
company-job-listings wraps the SyncGTM MCP company_job_listings tool: give it one company domain or name and it returns that company's open roles with job title, location and listing URL, up to 50 listings per call. It does not accept a LinkedIn company URL, and it returns no contact data. At a flat 1.5 credits per call whatever limit you set, it is the cheaper of the two single-company job tools — company_job_openings does the same job for 5.
What it does
- 1
Takes one company identifier — company_domain or company_name. The domain is the reliable input; company names collide across dozens of businesses.
- 2
Rejects LinkedIn company URLs. If that is all you have, resolve the domain with enrich_linkedin_page (0.5 credits) first, or call company_job_openings at 5 credits.
- 3
Filters at the source: job_title and job_title_exclude take arrays of titles, job_location and job_location_exclude take one location string each. Source filters are free and keep the response small.
- 4
Returns a jobs array with job title, location and the listing URL for each role. Up to 50 per call, but the default limit of 5 hides most of a mid-size company's board.
- 5
Returns no emails, no phone numbers and no hiring-manager names. Pair it with find_people_within_company when you need someone to contact.
- 6
Costs a flat 1.5 credits per call regardless of limit, so one company is one unit of spend.
How to use it
- 1
Download the skill file — it saves as company-job-listings.zip.
- 2
In Claude, open Settings → Capabilities → Skills and upload the .zip (or unzip the company-job-listings/ folder into .claude/skills/ for Claude Code).
- 3
Connect the SyncGTM MCP server — browser sign-in, no API key. Run check_credits (free) to confirm your balance before scoring a target list.
- 4
Trigger it by typing /company-job-listings and pasting a domain or a list of domains, plus the titles you care about — for example 'sales and RevOps roles only, exclude anything with Intern'.
- 5
The one setting worth tuning is limit. It accepts 1–50 and defaults to 5, and the cost is flat either way, so set it to 50 on every call.
Use cases
Account hiring check
Before a first call or a renewal, confirm whether the account is hiring into the function you sell to. Three open AE reqs turns a cold intro into a budget conversation.
Target list scoring
Run one call per domain across a named account list and rank accounts by how many relevant roles are open. Clusters of roles beat single backfills.
Personalized first lines
Quote the exact open req in your opening line — title, city and the listing URL — so the email reads as researched rather than blasted.
Territory expansion watch
Filter with job_location to spot an account staffing a new city or region. Catch the expansion before a competitor lands the office.
GTM workflow examples
Score a named account list by hiring intensity
- 1Run `check_credits` (free) to confirm the balance covers one 1.5-credit call per domain — 30 domains is 45 credits.
- 2Call `company_job_listings` once per domain with company_domain, limit 50, job_title set to your buying-function titles (Account Executive, Sales Development, Revenue Operations) and job_title_exclude set to Intern.
- 3Keep only the domains that returned 2 or more matching roles — a single opening is a backfill, a cluster is a team being built.
- 4Run `job_openings_growth_rate` (3 credits) on the top 10 clusters to separate real expansion from stale reposted reqs. Its `identifier` is a LinkedIn id, LinkedIn URL or company name — pass the name, not the domain.
- 5Call `find_people_within_company` on the survivors with `domain` plus `job_title` set to VP Sales or Head of RevOps, then `find_work_email` (1 credit) on each `linkedin_url` it returns — neither tool returns an email on its own.
Outcome: A ranked tier-1 list of accounts with open sales headcount, each row carrying a named budget owner and a verified work email.
Turn a LinkedIn-only account into a hiring-signal email
- 1Call `enrich_linkedin_page` (0.5 credits) on the company's LinkedIn URL to resolve its website domain — `company_job_listings` rejects LinkedIn URLs.
- 2Call `company_job_listings` with that company_domain, limit 50, and job_location set to the territory you own.
- 3Pick the req that names your category in its title — an ops or enablement role that will own the tooling you sell.
- 4Call `newly_hired_executives` with the same LinkedIn company URL as `company` and max_results 3 — it bills 0.5 credits per profile, so 3 profiles is 1.5 credits — to find the leader who joined recently and now owns that team.
- 5Draft the opener around the exact req title and city, with the listing URL pasted as proof.
Outcome: One personalized email per account that quotes a live job req and lands with the executive who just took ownership of the team posting it.
Monday hiring-signal digest across your book
- 1Call `company_job_listings` across the 20 domains in your open pipeline, limit 50, job_title filtered to the functions you sell into — 30 credits for the sweep.
- 2Diff this week's listing URLs against last week's saved run so the digest shows new reqs only.
- 3For any account with 3 or more new reqs, call `head_count_growth_rate` (2 credits) with the company name or LinkedIn URL as `identifier` to confirm the headcount trend backs the posting spike.
- 4Call `find_people_within_company` on the two strongest accounts to add a second thread into each live deal.
Outcome: A Monday digest of new job reqs per open opportunity, plus two named second contacts on the deals showing the fastest growth.
Prompts
Paste any of these into Claude once the skill is installed and the SyncGTM MCP is connected.
List every open role at stripe.com. Set limit to 50 and return job title, location and the listing URL as a table.Open roles at figma.com — sales and revenue operations titles only, exclude anything with Intern in the title. Limit 50.For these domains — stripe.com, figma.com, linear.app, ramp.com, vercel.com — list the open sales roles, one call per domain with limit 50. Use the domain, not the company name, and report total credits used at the end.List every open role at datadoghq.com with limit 50, but exclude anything located in New York. Use job_location_exclude at the source, do not trim the results after the call.I only have this LinkedIn page: https://www.linkedin.com/company/notion-hq. Resolve the domain with enrich_linkedin_page first, then list all open roles with limit 50. Do not use company_job_openings.Best practices
Pass company_domain, not company_name. 'Apex' matches a dozen companies; apex.com matches one.
Set limit to 50 on every call. The cost is flat at 1.5 credits whatever the limit, and the default of 5 hides most of a mid-size company's board.
Say 'do not use a LinkedIn URL' in the prompt. If a LinkedIn company page is sitting in context, your client can route to company_job_openings and spend 5 credits instead of 1.5.
Filter with job_title and job_title_exclude instead of trimming the output afterwards. Source filters are free and keep the response readable.
Cap the batch: 'stop after 20 companies and report credits used'. One call per company means a 100-domain list is 150 credits.
Reach for a cheaper sibling when the question is not about one named account — search_linkedin_job_openings at 0.3 credits for filtered market-wide search, linkedin_job_listings at 1 credit for plain keyword search. For hiring velocity over time use job_openings_growth_rate (3 credits), passing the company name or LinkedIn URL as its identifier; this tool returns a snapshot, not a trend.