Wiring a 1M-job index into Apify MCP: results need two calls, not one
StraightControl3377 · reddit · 2026-10-24
The author built a job index of 1 million live postings scraped from company career sites (Greenhouse, Lever, Workday—not LinkedIn/Indeed), refreshed daily, grown from JSON files on GitHub.
He put it on Apify and exposed it as an MCP tool to test whether Claude could use it without him writing a server—setup was a single URL, and runs took about 4 seconds, better than expected.
The gotcha: it takes two calls—the agent first invokes the actor with filters (country, category, experience level, remote), then must call get-dataset-items to actually read results. The first call looks like it returns nothing, which he initially mistook for a bug. He asks whether others have built MCP tools where data sits behind a second call; links to the MCP endpoint and actor page included.
More from coding & agent
- Disappointed with Codex, developer has it write a handoff file for Claude to take over — lxfater · 2026-10-24
- terrio v0.5.0 ships pure Rust geospatial engine with no GDAL, adds SQL and GRIB support — giswqs · 2026-10-24
- DeepSeek Flash-1017 pitfalls: broken budget counting, poor ambiguity handling, 'stingy' mode — karminski3 · 2026-10-24
- When AI agents disagree, who decides? Why the orchestrator shouldn't quietly become the decision-maker — Environmental_Fly371 · 2026-10-24
- A buyer's checklist: 12 questions to ask before adopting an MCP server vendor — pournasserian · 2026-10-24
- Claude Code project structure explained: CLAUDE.md, commands, skills and agents — Aiden_Tech_Ai · 2026-10-24