Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Greenhouse, Lever & Ashby ATS Hiring Signal Scraper

scrape_ats_job_board_hiring_signals
Read-onlyIdempotent

Extract active job openings, department hiring velocity, and B2B buying signals from Greenhouse, Lever, and Ashby career boards to identify companies expanding teams.

Instructions

Extract active job openings, department hiring velocity, and B2B buying signals from Greenhouse, Lever, and Ashby career boards ($0.50/1k).

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": {
      "companies": "<companies>"
    },
    "name": "scrape_ats_job_board_hiring_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
companiesYesCompany slugs or career URLs, e.g. ["stripe", "figma"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds genuinely useful non-schema context in the $0.50/1k cost note, but says nothing about rate limits, how invalid or unknown company slugs are handled, or how many companies can be batched per call.

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?

A single front-loaded sentence with no filler: verb, outputs, sources, and price all in one pass. Nothing is redundant given no output schema exists to restate.

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 one-param, no-output-schema tool this covers the essentials, and naming the three extracted signal types partly substitutes for the missing output schema. However, "department hiring velocity" and "B2B buying signals" are left undefined, leaving the agent unsure what shape of data to expect or how to interpret it.

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?

There is only one parameter and the schema already documents it at 100% coverage with a concrete example (["stripe", "figma"]). The description adds no further semantics such as accepted URL formats versus bare slugs, or whether mixed-ATS lists are allowed, so it sits at the baseline for a schema-complete single-param tool.

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 three concrete resources (active job openings, department hiring velocity, B2B buying signals) scoped to three named sources (Greenhouse, Lever, Ashby). This clearly separates it from the sibling jobs scraper (Wellfound/YC) without needing to reference it by name.

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?

The phrase "B2B buying signals" implies the intended use case (prospecting/signal detection), but there is no explicit when-to-use, when-not-to-use, or alternative routing. An agent must infer from its own task context whether this beats scrape_wellfound_yc_startup_jobs or the lead-scraping siblings.

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