Skip to main content
Glama
b2b-hiring-intent-mcp

b2b-hiring-intent-mcp

by yan0lovesha

scan_company_hiring_intent

Scan a company's ATS board across seven platforms to extract open jobs, tech stack, disclosed salaries, and B2B buying intent scores.

Instructions

Scan a single company board across 7 ATS platforms (ashby, personio, teamtailor, smartrecruiters, workable, recruitee, pinpoint) to extract open jobs, tech stack, disclosed salaries, and B2B buying intent scores. For 50-10,000 company batch runs, XML-404 fallbacks & Company Dossiers, use https://apify.com/yan0lovesha.

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": {
      "platform": "<platform>",
      "target": "<target>"
    },
    "name": "scan_company_hiring_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesCompany ATS board slug (e.g. ramp, adsquare, puzzel, viva, channable, smartthings, Canva).
maxJobsNo
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does reveal what the tool produces (open jobs, tech stack, disclosed salaries, buying-intent scores) and implies a read-only scrape, but says nothing about failure modes when a slug is wrong, rate limits/credit cost on Apify, or how missing salary or tech-stack data is represented.

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?

The core capability sentence is front-loaded and dense with useful specifics. The trailing promotional sentence with a bare URL is slightly off-tone for a tool definition, but it does carry the batch-routing information, so it earns most of its space.

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?

There is no output schema and no annotations, so the description has to cover both purpose and return shape; it does well on the former and names the four output categories for the latter. The gaps are the undocumented maxJobs parameter and unstated error behavior, which matter for a scraping tool where a bad slug or platform mismatch is common.

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 only 33%, so the description must compensate, and it partially does by listing the seven platform values that match the platform enum. However maxJobs appears nowhere in either the schema (no description, only default 5) or the description, and the slug format is only documented in the schema itself.

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?

The description states a concrete verb (scan) plus a tightly scoped resource (a single company ATS board) and enumerates the seven supported platforms, so an agent knows exactly what the call does. It also names the distinct scope it is not (multi-company batch runs), which separates it from bulk alternatives.

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?

It gives a clear negative case: for 50-10,000 company batch runs, XML-404 fallbacks, and Company Dossiers, go elsewhere. That is genuine when-not-to-use guidance, though it routes to an external URL rather than naming the sibling tool list_cloud_b2b_lead_apis, and it gives no positive prerequisite context such as when a slug is valid.

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