Job Listings in Claude: Pull Live LinkedIn Jobs via MCP (2026)
By Kushal Magar · September 29, 2026 · 12 min read
Key Takeaway
You can pull live LinkedIn job listings into Claude without touching a job board. Three SyncGTM MCP tools — search_linkedin_job_openings, company_job_openings, and job_openings_growth_rate — let job seekers build ranked shortlists and sales teams identify companies expanding their revenue teams, all from a single prompt.
Job listings in Claude means pulling live LinkedIn job data directly into a Claude conversation via the SyncGTM MCP, without opening a job board. You search, filter, score, and export listings using natural language prompts — no scraping, no extra accounts, no copy-pasting.
Scrolling job boards manually takes an average of 45–60 minutes to surface 20 quality-filtered roles. The same workflow via Claude and SyncGTM MCP takes under 5 minutes. This tutorial shows you exactly how.
This tutorial covers three SyncGTM MCP tools that make it possible: search_linkedin_job_openings for keyword and location searches, company_job_openings to list every open role at a target company, and job_openings_growth_rate to see who is hiring fastest. Job seekers use these to build a ranked shortlist. Sales teams use the same data as hiring signals to time outreach.
How do you pull job listings into Claude?
Connect the SyncGTM MCP to Claude Code with claude mcp add syncgtm -- npx -y @syncgtm/mcp-server, then prompt Claude to call search_linkedin_job_openings with your keyword, location, and date filter. Claude returns structured job data — title, company, location, posting date — that you can sort, filter, and export to CSV without leaving the conversation.
TL;DR
- Three tools, two use cases.
search_linkedin_job_openings,company_job_openings, andjob_openings_growth_ratevia SyncGTM MCP. - Job seekers: search by keyword, title, location, and date posted — get a ranked CSV shortlist in under 2 minutes.
- Sales teams: identify companies actively hiring revenue roles and use that as a trigger to time outreach.
- Credit cost: 1 credit per call across all three tools. Each call returns up to 25 results.
- No Apify, no scraping, no extra setup. One MCP connection gives Claude access to all three tools natively.
Who This Is For
This tutorial is for two audiences who use the same underlying data differently.
| Audience | How They Use Job Listings in Claude |
|---|---|
| Job seekers | Search by role + location, filter by recency, score jobs against a target criteria list, export a ranked CSV shortlist |
| Sales teams | Identify ICP companies actively hiring revenue roles as a buying signal, track hiring velocity to time outreach, research a target account's full open-role profile |
According to LinkedIn's Talent Insights, companies that increase job postings by 20%+ in a quarter are significantly more likely to be actively evaluating new software tools. That is the signal sales teams are looking for.
Prerequisites
You need two things before running your first job search in Claude.
- Claude Code installed — install via
npm install -g @anthropic-ai/claude-code. Requires Claude Pro ($20/mo) or Max ($100–$200/mo). - SyncGTM account — free tier available at syncgtm.com. Your SyncGTM API key is used to authenticate the MCP.
Connect the SyncGTM MCP
Run this once in your terminal to add SyncGTM as an MCP server for Claude Code:
claude mcp add syncgtm -- npx -y @syncgtm/mcp-server
When prompted, paste your SyncGTM API key. The connection is saved globally — you do not need to repeat this for future sessions.
Verify the connection
Start Claude Code and type: List available SyncGTM tools. Claude should list search_linkedin_job_openings, company_job_openings, and job_openings_growth_rate among the available tools.
Tool 1: search_linkedin_job_openings
This is the primary job search tool. It searches LinkedIn job listings by keyword, job title, location, and date posted — and returns structured results you can immediately work with.
Search parameters
| Parameter | What It Does | Example |
|---|---|---|
keyword | Full-text keyword search across title + description | “revenue operations” |
title | Filter by exact job title | “Account Executive” |
location | City, state, country, or “Remote” | “San Francisco, CA” |
date_posted | Filter recency of postings | “past_24_hours”, “past_week”, “past_month” |
limit | Max results per call (up to 25) | 25 |
Output columns
Each result returns:
job_id— unique LinkedIn job identifier (use for dedupe)title— job title as postedcompany— hiring company namelocation— city/country/remote statusposted_date— when the role was postedapply_url— direct link to applydescription_snippet— first 300 chars of the job description
Example prompt
Search LinkedIn for Account Executive roles posted in the last week in New York or Remote. Keyword: "SaaS sales". Limit 25 results. Show me a table with: title, company, location, posted_date, apply_url.
Multiple keyword searches in one session
You can run the tool multiple times within one conversation to cover multiple titles or locations. Claude accumulates all results in context so you can compare, filter, and export everything in a single follow-up:
Now search for "Enterprise Account Executive" in the same locations, also posted in the last week. Add those results to the previous list and remove any duplicates by job_id.
Tool 2: company_job_openings
company_job_openings lists every open role at a specific company. You pass a company name or LinkedIn company URL, and Claude returns all active postings on that company's page. Useful when you want to understand the full hiring picture at a target company — not just roles matching a keyword.
When to use it
- Job seekers: You found a company you want to work at — pull all their open roles at once instead of searching their website separately.
- Sales teams:You have a list of target accounts — pull each company's current job openings to see which departments are hiring. A company hiring 5 SDRs is a different conversation than one hiring 5 engineers.
Example prompt
Get all open job listings at Notion, HubSpot, and Linear right now. For each company, show me: company name, total open roles, list of titles, departments. Flag any companies with more than 3 open sales or revenue roles.
Batch a list of companies
You can pass a list of companies from a CSV and Claude will call the tool for each one:
Read accounts.csv (columns: company_name, domain). For each company, call company_job_openings and record: - total_open_roles - revenue_roles (titles containing SDR, AE, Sales, Account, RevOps) - engineering_roles - latest_posting_date Save to company-openings.csv. Sort by total_open_roles descending.
This gives you a ranked view of which accounts in your list are hiring most aggressively — a key signal for both job seekers targeting growth-stage companies and sales teams timing outreach.
Tool 3: job_openings_growth_rate
This tool returns a company's job posting growth rate — the percentage change in open roles over a defined lookback period (typically 30 or 90 days). It answers the question: which companies in my list are hiring fastest right now?
Why growth rate matters more than headcount
A company with 50 open roles today might have had 48 last month — flat. A company with 12 open roles today that had 4 last month grew 200%. The second company is the more interesting signal for both job seekers (companies that are accelerating tend to hire faster and pay better) and sales teams (rapid headcount expansion usually means budget expansion).
Output columns
| Column | Description |
|---|---|
company | Company name |
current_openings | Total open roles today |
prior_openings | Open roles in prior period |
growth_rate | Percentage change (+/−) |
lookback_days | Comparison window (30 or 90 days) |
Example prompt
Read accounts.csv. For each company, get the job openings growth rate over the last 30 days. Sort by growth_rate descending and save to hiring-velocity.csv. Flag companies with growth_rate > 50% in a separate column called "high_signal".
Sales tip: filter by department
After getting growth rates, follow up with company_job_openings on your high-signal companies to verify whether the growth is in revenue roles (SDR, AE, RevOps) or engineering. Revenue-role growth is the stronger buying signal for most sales tools.
Job Seeker Workflow: Build a Ranked Shortlist
Here is a complete workflow for a job seeker targeting Account Executive or Revenue Operations roles. Adapt the titles and locations to your search.
Step 1: Broad search
Search LinkedIn for "Account Executive" roles posted in the last 7 days. Locations: New York, San Francisco, Austin, Remote. Keyword: "SaaS". Limit 25. Return a table: title, company, location, posted_date, apply_url.
Step 2: Score against your criteria
Score each job from 1 to 10 based on these criteria: - Company stage: Series B or later = +3 points - Remote or hybrid = +2 points - Posted in last 48 hours = +2 points - Title matches "Enterprise" or "Strategic" = +1 point - Company headcount 100–1000 = +2 points Add a score column and sort descending. Remove any with score < 5.
Step 3: Research top companies
For the top 5 companies by score, call company_job_openings. I want to know: how many total roles are they hiring for? Are they growing or contracting? What departments are expanding? Add this context as notes to my shortlist.
In roughly 5 minutes, you have a scored, researched shortlist of the best-fit roles posted this week — something that takes 45–60 minutes manually across multiple job boards.
Sales Team Workflow: Hiring as a Buying Signal
When a company starts hiring SDRs, AEs, or RevOps managers, they are expanding their go-to-market motion. That is exactly when they are most likely to evaluate new tools — before the new hires start, not after. Gartner research on B2B buying journeys shows that 83% of the purchase decision happens before a vendor is ever contacted — which means the window to reach an expanding team is narrow. Here is how to use job listing data to time that outreach.
Step 1: Score your target account list by hiring velocity
Read icp-accounts.csv (columns: company_name, domain). For each company: 1. Call job_openings_growth_rate (30-day lookback) 2. Call company_job_openings Build a priority_score from 1–10: - growth_rate > 50% = +4 - growth_rate 20–50% = +2 - revenue_roles > 3 = +3 - revenue_roles 1–3 = +1 - any VP Sales or CRO role open = +3 Save to account-signals.csv sorted by priority_score descending. Output only accounts with priority_score >= 5.
Step 2: Personalize outreach using job data
For each high-signal account, pull their specific open roles and use that in your outreach context:
For the top 10 accounts from account-signals.csv, draft a cold email opening line that references their hiring context. Use this format: "[Company] is currently hiring [X] revenue roles — that kind of growth usually comes with [relevant pain point we solve]." One opening line per company. Keep it under 25 words.
Why this works
Mentioning a prospect's active hiring shows you did real research — not just “I saw you work at X.” It anchors the email in something they are actively managing right now. You can learn more about combining job signal data with B2B enrichment in Claude for a complete account research workflow.
Dedupe and CSV Export
When you run multiple searches — different keywords, multiple locations, different date ranges — you will get overlapping results. Here is how to handle dedupe and export cleanly.
Dedupe by job_id
Every job listing has a unique job_id. Use it as your dedupe key across searches:
Combine all job results from this session into a single list. Remove any rows where job_id appears more than once (keep the first). Count how many duplicates were removed and tell me the final count.
Export to CSV
Save the deduped results to jobs-shortlist.csv with these columns: job_id, title, company, location, posted_date, score, apply_url, notes Sort by score descending, then by posted_date newest first.
Track what you have already applied to
Read applied-jobs.csv (column: job_id). From jobs-shortlist.csv, remove any jobs where job_id already appears in applied-jobs.csv. Save the remaining jobs to new-jobs.csv.
Maintain a running applied-jobs.csv file and Claude will never show you a role you already processed.
Credit Costs per Search
SyncGTM charges per tool call, not per result. Here is what each tool costs and how to budget a typical session.
| Tool | Credit Cost | Results per Call |
|---|---|---|
search_linkedin_job_openings | 1 credit per call | Up to 25 jobs |
company_job_openings | 1 credit per company | All open roles at that company |
job_openings_growth_rate | 1 credit per company | Growth rate + current/prior count |
Typical session cost
- Job seeker shortlist session (3 keyword searches + 5 company lookups): 3 + 5 = 8 credits
- Sales signal scoring session (50 accounts × growth rate + top 10 company openings): 50 + 10 = 60 credits
Check your credit balance
Ask Claude at any point: How many SyncGTM credits do I have remaining? Claude will call check_credits and return your current balance before continuing.
Common Mistakes When Pulling Job Listings in Claude
1. Using only keyword search instead of title + keyword
A keyword search for “revenue operations” returns roles with that phrase anywhere in the description — including tangentially related roles. Combine title with keyword to tighten results. Example: title="RevOps Manager", keyword="HubSpot".
2. Running multiple searches without deduping
If you search “Account Executive New York” and then “Account Executive Remote,” companies with remote-eligible NY-based roles appear in both results. Always dedupe by job_id before scoring or exporting.
3. Treating job_openings_growth_rate as a standalone signal
High growth rate is interesting, but a company going from 2 to 6 open roles (200% growth) is less significant than one going from 20 to 35 (75% growth on real volume). Always check current_openings alongside the percentage to avoid prioritizing noise.
4. Not saving session state to a file
Claude Code sessions are not persistent. If you close the terminal, your accumulated results are gone. Always ask Claude to save intermediate results to a CSV file before ending a session, especially for long enrichment runs.
5. Applying to all roles on your shortlist at once
For job seekers: a shortlist of 40 roles is not 40 equal opportunities. After scoring, focus your application energy on the top 5–8 roles where you score highest against their criteria. Quality of application beats quantity every time.
Conclusion
Pulling job listings into Claude changes what is possible. Job seekers get a scored, deduplicated shortlist across multiple keywords and locations in under 5 minutes. Sales teams get a ranked account list weighted by real hiring velocity — the kind of signal that tells you exactly when to reach out.
All three tools — search_linkedin_job_openings, company_job_openings, and job_openings_growth_rate — are available the moment you connect SyncGTM as your MCP. No Apify account, no scraping setup, no separate API keys. One connection, three tools, two workflows that work immediately.
If you want to go deeper — combine job signal data with CRM enrichment via HubSpot MCP or Salesforce MCP to push high-signal accounts directly into your pipeline without leaving Claude.