Skip to main content
Glama
ClearStack Data MCP server

ClearStack Data MCP server

by Wordhalm

Search company career sites

search_ats_jobs
Read-only

Find open roles on company career sites across Greenhouse, Lever, Ashby, and SmartRecruiters; filter by keywords, location, company, or remote status to support job search and hiring signals.

Instructions

List open roles straight from company career sites on Greenhouse, Lever, Ashby and SmartRecruiters (index of 25,787 employers). Use it for job search ("remote AI engineer roles at Anthropic, OpenAI, Linear") or hiring signals ("is Datadog hiring data engineers?"). Returns title, location, team, publish date and apply URL. Cost on the user's Apify account: $0.002 per call + $0.0015 per job returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_ats_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxJobsNoMaximum jobs to return (and pay for).
keywordsNoMatch any of these in the job title or department, e.g. ["AI Engineer", "Product Manager"]. Empty = all roles.
locationNoCase-insensitive substring of the job location, e.g. "London", "Remote", "Germany".
companiesNoCompany names ("Stripe"), ats:slug pairs ("greenhouse:stripe", "ashby:openai") or job board URLs. Empty = 35 well-known tech and AI employers.
remoteOnlyNoOnly roles marked remote.

Output Schema

NameRequiredDescriptionDefault
actorYesApify Actor that produced the data
itemsYes
runIdYesApify run ID; pass it to get_run_results if finished is false
statusYesApify run status, e.g. SUCCEEDED or RUNNING
finishedYesfalse when the run was still going and items are partial
itemCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-redundant behavior: per-call and per-job cost charged to the user's Apify account, plus the fact that maxJobs is also what you pay for, which materially affects invocation choices.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences in a sensible order: capability, example use cases, return fields, then cost. Nothing is padded and the highest-value information (what it searches and what it costs) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need only a brief mention, and the description supplies exactly that plus a cost model that annotations and schema cannot express. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains keywords, location, companies and remoteOnly in detail. The description's example query ('remote AI engineer roles at Anthropic, OpenAI, Linear') loosely illustrates combining companies with keywords, but adds no syntax or scope detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List open roles straight from company career sites'), names the exact sources (Greenhouse, Lever, Ashby, SmartRecruiters) and the index size, so an agent can instantly distinguish it from verify_eu_company or search_google_ads.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides concrete usage contexts – job search queries and hiring-signal questions ('is Datadog hiring data engineers?') – which is clear when-to-use guidance. It does not name an alternative tool or state exclusions, which keeps it short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.