Generect Live API MCP Server

Official

Overview Schema Source Related Servers Discussions(1)Admin

Find a verified work email

generate_email

Find and verify a person's work email by lead ID, LinkedIn URL, or name and company domain, with batch support for resolving multiple contacts.

Instructions

Find and verify a work email. Billable: about $0.02 per VALID email found (a miss is free) at the Tier 0 list price. Accounts can pay a different rate: get_balance returns this account's prices, and every response reports what was actually spent in cost.amount_charged_usd. Identifies the person by lead_id (most accurate), LinkedIn URL or first name, last name and domain. candidates resolves several people in one call; more than 10 go to an async bulk job instead, which returns a job_id for get_bulk_job.

Input Schema

Name	Required	Description
`domain`	No	Company domain without protocol, e.g. "stripe.com" (name+domain mode).
`lead_id`	No	Generect lead id from search / preview / enrich results — the cheapest and most accurate identifier.
`last_name`	No	Last name (name+domain mode).
`candidates`	No	Batch mode. Each entry uses the same identifier rules as the single-person form.
`first_name`	No	First name (name+domain mode).
`timeout_ms`	No	Request timeout in milliseconds.
`middle_name`	No	Middle name (optional, improves pattern matching).
`linkedin_url`	No	LinkedIn profile URL.

Output Schema

Name	Required	Description	Default
`job`	No
`cost`	No
`mode`	No
`dropped`	No
`results`	No
`next_step`	No
`requested`	No
`submitted`	No
`test_mode`	No
`test_mode_notice`	No
`vocabulary_warnings`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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
```
- removedInput schema / properties / candidates / items / additionalProperties
```
Removed value: -false
```
- 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 / results / items
```
Added value: +{}
```
- addedOutput schema / properties / vocabulary_warnings / items
```
Added value: +{}
```

Changed10 schema fields changedv0.9.0Sep 24, 2026

addedInput schema / properties / candidates

Added value: +{
+  "description": "Batch mode. Each entry uses the same identifier rules as the single-person form.",
+  "items": {
+    "additionalProperties": false,
+    "description": "One of: {lead_id} | {linkedin_url} | {first_name,last_name,domain}",
+    "properties": {
+      "domain": {
+        "type": "string"
+      },
+      "first_name": {
+        "type": "string"
+      },
+      "last_name": {
+        "type": "string"
+      },
+      "lead_id": {
+        "type": "string"
+      },
+      "linkedin_url": {
+        "type": "string"
+      },
+      "middle_name": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

changedInput schema / properties / domain / description

Previous value: -"Company domain without protocol (e.g., generect.com)"New value: +"Company domain without protocol, e.g. \"stripe.com\" (name+domain mode)."

changedInput schema / properties / first_name / description

Previous value: -"First name of the person"New value: +"First name (name+domain mode)."

changedInput schema / properties / last_name / description

Previous value: -"Last name of the person"New value: +"Last name (name+domain mode)."

addedInput schema / properties / lead_id

Added value: +{
+  "description": "Generect lead id from search / preview / enrich results — the cheapest and most accurate identifier.",
+  "type": "string"
+}

addedInput schema / properties / linkedin_url

Added value: +{
+  "description": "LinkedIn profile URL.",
+  "type": "string"
+}

addedInput schema / properties / middle_name

Added value: +{
+  "description": "Middle name (optional, improves pattern matching).",
+  "type": "string"
+}

changedInput schema / properties / timeout_ms / description

Previous value: -"Request timeout in milliseconds"New value: +"Request timeout in milliseconds."

removedInput schema / required

Removed value: -[
-  "first_name",
-  "last_name",
-  "domain"
-]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "cost": {
+      "additionalProperties": false,
+      "properties": {
+        "amount_charged_usd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "billed": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "operation": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "deprecated_params_ignored": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "dropped": {
+      "type": "number"
+    },
+    "job": {},
+    "mode": {
+      "type": "string"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "requested": {
+      "type": "number"
+    },
+    "results": {
+      "type": "array"
+    },
+    "submitted": {
+      "type": "number"
+    },
+    "test_mode": {
+      "type": "boolean"
+    },
+    "test_mode_notice": {
+      "type": "string"
+    },
+    "vocabulary_warnings": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true) by disclosing the cost model: ~$0.02 per valid email, free on a miss, tier list price, per-account variance, and the exact response field cost.amount_charged_usd for actual spend. This is precisely the billing/consumption context an agent needs before calling a metered, non-read-only tool.

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-loads the purpose in a five-word sentence, then layers billing, identification, and batch routing in a tight block with no filler. Slightly dense — the billing and routing clauses are packed into one paragraph — but every sentence carries information.

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

Completeness4/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 values needn't be explained, and the description still calls out cost.amount_charged_usd for the one field agents care about. Billing, identifier modes, and bulk escalation are all covered; the only gap is that with 0 required parameters it never states that at least one identifier must be supplied.

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 description coverage is 100%, so the baseline is 3; the description adds genuine selection guidance by declaring lead_id "most accurate" and spelling out the three identification forms (lead_id, LinkedIn URL, name+domain). It does not document timeout_ms or explain why zero parameters are marked required, but it meaningfully enhances the already-documented schema.

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 and resource: "Find and verify a work email," which is immediately actionable. It does not explicitly distinguish itself from the closest sibling validate_email (which checks an email you already have), so an agent must infer that boundary from names alone. Clear but not sibling-differentiated.

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?

Explicitly ranks identifier modes ("lead_id (most accurate)"), explains that `candidates` handles several people in one call, and routes requests over 10 to an async bulk job that "returns a job_id for get_bulk_job." It also names get_balance for account-specific pricing, leaving nothing ambiguous about which tool to invoke next.

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