Skip to main content
Glama
ceadigital-mcp-tools

ceadigital-mcp-tools

Official
by ceadigital

hiring_intent_jobs_scraper

Query public Greenhouse and Lever ATS boards to find live job postings, tech-stack signals, and B2B hiring urgency scores for targeted outreach.

Instructions

Query public Greenhouse & Lever ATS boards for live job postings, tech-stack signals, and B2B hiring urgency scores. (Free 1-row preview automatic when CEA_API_KEY is unset; Apify: cea_digital/hiring-intent-jobs-scraper)

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": {
      "query": "<query>"
    },
    "name": "hiring_intent_jobs_scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPrimary target query, domain, URL, or identifier (default: "stripe")stripe
secondaryNoOptional secondary filter (address, condition, permit type, role keyword, or language).engineer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two valuable behaviors: an automatic free 1-row preview without an API key, and that the backend is the Apify actor cea_digital/hiring-intent-jobs-scraper. It still omits cost/pagination behavior of the paid path, rate limits, and how many rows a normal run returns.

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 with the capability front-loaded and the operational caveat in parentheses. Lean and easy to scan; the Apify actor identifier borders on metadata but is a useful pointer for the paid path.

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

Completeness3/5

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

For a two-parameter scrape with no output schema, the description does enumerate the kinds of results returned, which is adequate. It stops short of describing output shape, result volume, or the difference in behavior between keyed and unkeyed runs, leaving some gaps an agent would want filled.

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 coverage is 100%, so both parameters are already documented and the baseline is 3. The description adds nothing about how 'query' is interpreted (company name vs. board token vs. URL) or how 'secondary' constrains results, so it does not earn above 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 (query) and a precisely scoped resource (public Greenhouse & Lever ATS boards), plus the three things it yields: live job postings, tech-stack signals, and B2B hiring urgency scores. No sibling among the listed tools touches ATS boards, so no differentiation text is needed.

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 only implied by the phrase 'B2B hiring urgency scores' – an agent can infer this is for hiring-intent lead generation, but there is no explicit when-to-use, when-not-to-use, or alternative recommendation. The one genuinely operational note is the free-preview fallback when CEA_API_KEY is unset.

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