Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Wellfound & YC Startup Jobs, Founders & Hiring Leads

scrape_wellfound_yc_startup_jobs
Read-onlyIdempotent

Extract actively hiring startups from Wellfound and Y Combinator with domains, team sizes, batch stage, ATS career links, LinkedIn URLs, and verified contact emails.

Instructions

Extract actively hiring startups from Wellfound & Y Combinator directories with startup domains, team sizes, batch/stage, ATS career links, LinkedIn URLs, and verified contact emails ($0.75/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": {
      "queries": "<queries>"
    },
    "name": "scrape_wellfound_yc_startup_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesStartup industry or role keywords, e.g. ["AI agent", "Fintech", "Developer tools"]
maxStartupsNoMaximum hiring startups

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: the source directories are live third-party sites (consistent with openWorldHint) and the cost is disclosed at $0.75/1k, which matters for a paid extraction tool. It stops short of covering rate limits, credits, or what happens when a startup lacks a verified email.

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 front-loaded sentence with the verb and sources first, then the output fields, then the price. The field list is dense but each token maps to concrete return data; nothing is redundant.

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?

With no output schema, the description does carry the burden of describing return values and does so by enumerating the produced fields. However, it omits result-shape details an agent would want for a scraping tool: pagination, deduplication across the two directories, and what 'verified' emails actually mean.

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%: 'queries' already carries keyword examples and 'maxStartups' has a default and explanation. The description adds no further semantics such as how multiple queries combine (union vs. intersection) or whether maxStartups is per-query or total, so it sits at the baseline.

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

Purpose4/5

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

States a specific verb ('Extract') and a precise resource ('actively hiring startups from Wellfound & Y Combinator directories'), plus the exact fields returned. The named source directories distinguish it from adjacent siblings like scrape_funded_startups_sec_form_d and scrape_ats_job_board_hiring_signals, though those alternatives are never explicitly acknowledged.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no routing to alternatives. An agent must infer from 'actively hiring startups' that this is for hiring-signal lead generation, and must guess how it differs from the ATS job board or SEC Form D startup tools in the catalog.

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