Generect Live API MCP Server

Official

Overview Schema Source Related Servers Discussions(1)Admin

Enrich a lead by LinkedIn URL (alias)

get_lead_by_url

Enrich lead data from a LinkedIn profile URL. Use this alias for backward compatibility to retrieve enriched lead records.

Instructions

Alias of enrich_lead for a LinkedIn profile URL, kept for backwards compatibility. Billable: about $0.02 per record found (not-found is refunded) 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. enrich_lead does the same and also accepts a Generect id (the most accurate identifier) or an email for reverse lookup.

Input Schema

Name	Required	Description
`url`	Yes	LinkedIn profile URL (e.g. https://www.linkedin.com/in/username/).
`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 recent cached record is good enough and cost matters more than freshness.
`posts`	No	DEPRECATED — accepted but ignored. Removed: v1 enrich returns the full profile without per-section toggles.
`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.
`comments`	No	DEPRECATED — accepted but ignored. Removed: v1 enrich returns the full profile without per-section toggles.
`timeout_ms`	No	Request timeout in milliseconds.
`inexact_company`	No	DEPRECATED — accepted but ignored. Removed: v1 enrich matches on the identifier you pass.
`people_also_viewed`	No	DEPRECATED — accepted but ignored. Removed: v1 enrich returns the full profile without per-section toggles.

Output 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 recent cached record 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 recent cached record 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: +{}
```

Changed13 schema fields changedv0.9.0Sep 24, 2026

changedInput schema / properties / comments / description

Previous value: -"Include comments data"New value: +"DEPRECATED — accepted but ignored. Removed: v1 enrich returns the full profile without per-section toggles."

removedInput schema / properties / comments / type
```
Removed value: -"boolean"
```

addedInput schema / properties / compact

Added value: +{
+  "description": "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.",
+  "type": "boolean"
+}

changedInput schema / properties / inexact_company / description

Previous value: -"Allow inexact company matching"New value: +"DEPRECATED — accepted but ignored. Removed: v1 enrich matches on the identifier you pass."

removedInput schema / properties / inexact_company / type
```
Removed value: -"boolean"
```

addedInput schema / properties / mode

Added value: +{
+  "description": "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 recent cached record is good enough and cost matters more than freshness.",
+  "enum": [
+    "auto",
+    "database",
+    "realtime"
+  ],
+  "type": "string"
+}

changedInput schema / properties / people_also_viewed / description

Previous value: -"Include people also viewed"New value: +"DEPRECATED — accepted but ignored. Removed: v1 enrich returns the full profile without per-section toggles."

removedInput schema / properties / people_also_viewed / type
```
Removed value: -"boolean"
```

changedInput schema / properties / posts / description

Previous value: -"Include posts data"New value: +"DEPRECATED — accepted but ignored. Removed: v1 enrich returns the full profile without per-section toggles."

removedInput schema / properties / posts / type
```
Removed value: -"boolean"
```

changedInput schema / properties / timeout_ms / description

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

changedInput schema / properties / url / description

Previous value: -"LinkedIn profile URL (e.g., https://www.linkedin.com/in/username/)"New value: +"LinkedIn profile URL (e.g. https://www.linkedin.com/in/username/)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "company": {},
+    "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"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "lead": {},
+    "mode": {
+      "type": "string"
+    },
+    "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?

Beyond the annotations, the description discloses billing behavior: roughly $0.02 per found record, refunds for not-found results, tiered account-specific pricing, and the exact response field cost.amount_charged_usd that reports actual spend. It also points to get_balance for account pricing. Those details materially help an agent understand cost implications before invocation.

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 description is front-loaded with the alias identity and then adds pricing and sibling comparison. Every sentence is relevant, though the pricing and cost-reporting detail is somewhat dense and could be trimmed slightly without losing key 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?

Given the rich input schema, 100% parameter coverage, annotations, and the existence of an output schema, the description supplies the additional context an agent needs: alias status, backward-compatibility purpose, billing implications, and the main alternative. Return value details are appropriately omitted because the output schema covers them.

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%, so parameter documentation is already complete. The description reinforces the URL input and notes that enrich_lead additionally accepts id/email, but it adds no meaningful detail about mode, compact, timeout_ms, or the deprecated ignored parameters. Baseline 3 is appropriate.

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 immediately states that this is an alias of enrich_lead scoped to a LinkedIn profile URL. It explicitly distinguishes the tool from enrich_lead, which accepts a Generect id or email, so an agent can identify both the verb and the narrower resource scope without opening the schema.

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 explains that the tool is kept for backwards compatibility and that enrich_lead does the same plus accepts id/email, which gives clear context for when enrich_lead is the better sibling. It stops short of an explicit 'use enrich_lead for new integrations' exclusion, so the guidance is strong but not fully prescriptive.

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