Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_multi_ats_jobs

Read-onlyIdempotent

Search multiple ATS career boards and extract normalized job openings from Ashby, Greenhouse, Lever, Workable, and SmartRecruiters, filtered by keywords, remote status, and result limits.

Instructions

Extract normalized job openings across Ashby, Greenhouse, Lever, Workable, and SmartRecruiters career boards with departments, remote flags, compensation bands, and direct apply links (corridordata/multi-ats-startup-jobs-enricher).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "boards": "<boards>"
    },
    "name": "search_multi_ats_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardsYesATS board URLs or `provider:slug` identifiers (e.g. ['ashby:linear', 'greenhouse:cloudflare', 'lever:palantir']).
keywordsNoOptional role, department, or location keywords.
maxItemsNoMaximum normalized ATS job postings to return.
remoteOnlyNoOnly return roles explicitly marked Remote.
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds useful output-shape context (departments, remote flags, compensation bands, apply links) and names the underlying Apify actor, but says nothing about billing/charging behavior, rate limits, or empty-board handling that the maxTotalChargeUsd parameter hints at.

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

Conciseness4/5

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

A single dense sentence, front-loaded with the verb and provider list, with the returned fields grouped afterward. No filler, though the parenthetical actor identifier is arguably noise for an invoking agent.

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

Completeness4/5

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

With no output schema, the description usefully enumerates the fields returned, and all five parameters are fully documented in the schema. It is missing only guidance on provider/board identifier expectations beyond the schema and any cost/scale caveats for a five-provider fan-out.

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%, including the boards format examples, defaults, and the Apify PPE charge cap. The description adds no parameter-level meaning beyond that baseline.

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 ('Extract') and resource ('normalized job openings') and enumerates the five ATS providers covered. An agent can distinguish this job-board search from grant/tender/pricing siblings without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by naming the supported ATS boards, but there is no explicit when-to-use, when-not-to-use, or alternative routing among the many search_* siblings. The agent must infer that this is the job-posting tool rather than being told.

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