Generect Live API MCP Server

Official

Overview Schema Source Related Servers Discussions(1)Admin

Enrich one lead

enrich_lead

Enrich one known lead's full profile by Generect id, LinkedIn URL, or work email reverse lookup. Returns contact and company details; billed per record found, not-found lookups are free.

Instructions

Full profile for ONE known person, by Generect id, LinkedIn URL, or work email (reverse lookup). BILLABLE — about $0.0067 per record found (not-found is refunded) (Tier 0 list price; your account may pay a different rate — call get_balance for your real prices, and read cost.amount_charged in every response for what was actually spent). Not found costs nothing. Prefer the id from a search/preview result — it is the most accurate identifier. For many people at once use start_bulk_job.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Generect lead id from search/preview.
`mode`	No	Data mode. "database" = Generect's own index: sub-second, free counts, free thin rows (see detail) or cheaper full rows; it accepts a subset of the filters today and names any it rejects. "realtime" = live LinkedIn lookup, 5–60s, billed per row, accepts every realtime filter. "auto" (default) tries database first and escalates to realtime only if a filter you passed is rejected there (the escalation is reported, and is refused above the per-call spend ceiling). Pick "database" explicitly when a record from the last 12 months is good enough and cost matters more than freshness.
`email`	No	Work email, for reverse lookup.
`compact`	No	Default true: return a small per-lead summary (including the Generect `id`, which every later step accepts). Set false for the full raw record (~80 fields) — only worth it when you specifically need skills, education or other deep fields.
`timeout_ms`	No	Request timeout in milliseconds.
`linkedin_url`	No	LinkedIn profile URL.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cost`	No
`lead`	No
`mode`	No
`found`	No
`company`	No
`test_mode`	No
`test_mode_notice`	No
`vocabulary_warnings`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.12.2Oct 16, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / mode / description

Previous value: -"Data mode. \"database\" = cached, sub-second, cheaper, free counts, core filters only. \"realtime\" = live LinkedIn lookup, 5–60s, pricier, supports every filter. \"auto\" (default) tries database first and only escalates to realtime if a filter you passed is unsupported there — an escalation is reported in the response. Pick \"database\" explicitly when a record from the last 12 months is good enough and cost matters more than freshness."New value: +"Data mode. \"database\" = Generect's own index: sub-second, free counts, free thin rows (see detail) or cheaper full rows; it accepts a subset of the filters today and names any it rejects. \"realtime\" = live LinkedIn lookup, 5–60s, billed per row, accepts every realtime filter. \"auto\" (default) tries database first and escalates to realtime only if a filter you passed is rejected there (the escalation is reported, and is refused above the per-call spend ceiling). Pick \"database\" explicitly when a record from the last 12 months is good enough and cost matters more than freshness."

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / deprecated_params_ignored / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / vocabulary_warnings / items
```
Added value: +{}
```

Addedv0.9.0Sep 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description goes well beyond that with billing mechanics (BILLABLE, ~$0.0067 per found record, not-found refunded, Tier 0 list price caveat, cost.amount_charged in every response), the per-call spend ceiling that can refuse an escalation, escalation reporting, and realtime latency of 5-60s.

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?

Front-loaded with what the tool returns and its cost, then routing guidance. Dense parenthetical stacking (price caveat plus get_balance plus amount_charged all in one clause) costs some readability, but essentially every sentence carries actionable information.

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

Completeness5/5

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

An output schema exists, so return format need not be explained, yet the description still tells the agent where to read actual spend. Combined with identifier choice, mode selection, billing, and bulk-tool routing, nothing needed to invoke this correctly or decide whether to invoke it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds selection guidance the schema does not: it frames id/LinkedIn/email as interchangeable identifiers and states that `id` is the most accurate one, which is a cross-parameter preference rather than a restatement of the schema text.

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+resource+scope: 'Full profile for ONE known person, by Generect id, LinkedIn URL, or work email (reverse lookup).' The 'ONE' emphasis and the explicit 'For many people at once use start_bulk_job' cleanly separate it from the bulk sibling, and 'known person' separates it from search/preview tools.

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

Usage Guidelines5/5

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

Gives explicit routing rules: prefer the `id` from a search/preview result as the most accurate identifier, and use start_bulk_job for many people. It also explains when to pick each `mode` value, including the concrete case for choosing 'database' explicitly ('when a record from the last 12 months is good enough and cost matters more than freshness').

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

Deploy Server