generect-mcp

Enrich a lead by LinkedIn URL (alias)

get_lead_by_url

Read-only

Alias of enrich_lead for a LinkedIn profile URL, kept for backwards compatibility. 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). Prefer enrich_lead — it also accepts a Generect id (cheaper to get right) or an email for reverse lookup.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	LinkedIn profile URL (e.g. https://www.linkedin.com/in/username/).
`mode`	No	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.
`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

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.

Changed1 schema field changedSep 24, 2026

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"
+}

Changed12 schema fields changedSep 10, 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/)."

First observedFeb 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses billing behavior, approximate cost, refund policy for not-found records, and where to find actual spend in the response. It also clarifies that the tool is an alias, which transparently signals that behavior mirrors enrich_lead.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: alias and purpose come first, followed by cost, then the routing guidance. It is only a few sentences and every clause earns its place, including the pricing note and the pointer to get_balance.

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?

For a tool with 8 parameters, an output schema, and rich annotations, this description is complete. It covers what the tool is, what it costs, how failures are billed, and which sibling to prefer. No critical operational guidance is missing.

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 the schema already documents every parameter thoroughly. The description adds no per-parameter semantics; it focuses on cost and alias behavior. Per the calibration baseline, this is adequate but not additive.

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 opens by stating it is an alias of enrich_lead specifically for a LinkedIn profile URL, kept for backwards compatibility. This clearly identifies the resource (a lead), the action (enrich), the input shape (LinkedIn URL), and how it relates to its sibling enrich_lead.

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?

The description explicitly routes agents to the preferred sibling: 'Prefer enrich_lead — it also accepts a Generect id (cheaper to get right) or an email for reverse lookup.' This gives a concrete when-to-use vs. when-not-to-use rule and names the alternative, leaving little to inference.

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

All generect-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.