Generect Live API MCP Server

Official

by generect

Overview Schema Source Related Servers Discussions(1)Admin

TypeScript

Hybrid

Search companies (billed per row)

search_companies

Read-only

Find companies matching your ideal customer profile by industry, location, headcount, and more. Filter and retrieve targeted company lists for B2B lead generation.

Instructions

Return companies matching an ICP. BILLABLE — about $0.0067 per returned row (0 rows costs $0) (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). Run count_companies first. Note that headcount_range is a snapshot taken when the record was indexed and can lag the company's current size; the filter itself is applied at query time.

Input Schema

TableJSON Schema

Name	Required	Description
`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 freshness is not critical and cost matters more than freshness.
`limit`	No	Alias for limit_by.
`offset`	No	Alias for offset_by.
`compact`	No	Default true: return a small per-company 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.
`keywords`	No	Free-text keywords across name/description/specialties — realtime only: using it forces the pricier live mode.
`limit_by`	No	Rows to return this call (1–100, default 25). You are billed per returned row, so this number IS the price of the call.
`locations`	No	HQ locations — cities, states or countries.
`offset_by`	No	Rows to skip (pagination).
`headcounts`	No	Size buckets. Allowed ONLY: "1-10","11-50","51-200","201-500","501-1000","1001-5000","5001-10000","10 000+".
`industries`	No	Company industries. Must match Generect industry names exactly (e.g. "Software Development"); unknown names are rejected with HTTP 400.
`timeout_ms`	No	Request timeout in milliseconds.
`exclude_ids`	No	Exclude companies by LinkedIn id/URN.
`technologies`	No	Technologies the company uses — realtime only: using it forces the pricier live mode.
`company_names`	No	Restrict to specific company names — realtime only: using it forces the pricier live mode.
`company_types`	No	Company types: "Public Company","Privately Held","Non Profit","Government Agency","Educational", …
`revenues_range`	No	Annual revenue range, single object {min,max} — realtime only: using it forces the pricier live mode.
`sub_industries`	No	Expand each selected industry to its sub-industries as well (broadens the match).
`exclude_domains`	No	Exclude companies by domain (e.g. existing customers).
`linkedins_links`	No	Specific LinkedIn company URLs — realtime only: using it forces the pricier live mode.
`headcount_growth`	No	Headcount growth in percent — realtime only: using it forces the pricier live mode.
`num_of_followers`	No	LinkedIn follower buckets: "1-50","51-100","101-1000","1001-5000","5001+" — realtime only: using it forces the pricier live mode.
`confirm_spend_usd`	No	Explicit approval for an unusually large charge. Calls whose worst case exceeds $5 are refused unless this is set to at least the amount the tool reports. Only set it after the user has agreed to that number.
`exclude_locations`	No	HQ locations to exclude.
`get_max_companies`	No	DEPRECATED — accepted but ignored. Always on now: search responses include results_count without asking.
`exclude_industries`	No	Industries to exclude.
`hiring_on_linkedin`	No	Only companies actively hiring — realtime only: using it forces the pricier live mode.
`fallback_from_leads`	No	DEPRECATED — accepted but ignored. Removed. It fabricated lead-derived name aggregates and cost an extra billable query.
`department_headcount`	No	Department size, e.g. {"name":"engineering","min":10,"max":100} — realtime only: using it forces the pricier live mode.
`allow_unlisted_values`	No	Escape hatch for the local vocabulary check — see the lead-side field of the same name.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`fix`	No
`cost`	No
`mode`	No
`note`	No
`leads`	No
`status`	No
`returned`	No
`companies`	No
`test_mode`	No
`spend_guard`	No
`results_count`	No
`next_page_args`	No
`requested_rows`	No
`escalation_note`	No
`test_mode_notice`	No
`vocabulary_warnings`	No
`blocked_by_vocabulary`	No
`deprecated_params_ignored`	No
`escalated_to_realtime_because`	No
`api_returned_more_than_requested`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed32 schema fields changedv0.9.0Sep 24, 2026

addedInput schema / properties / allow_unlisted_values

Added value: +{
+  "description": "Escape hatch for the local vocabulary check — see the lead-side field of the same name.",
+  "type": "boolean"
+}

changedInput schema / properties / compact / description

Previous value: -"Return compact summary instead of full JSON"New value: +"Default true: return a small per-company 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."

addedInput schema / properties / company_names

Added value: +{
+  "description": "Restrict to specific company names — realtime only: using it forces the pricier live mode.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / company_types / description

Previous value: -"Company types"New value: +"Company types: \"Public Company\",\"Privately Held\",\"Non Profit\",\"Government Agency\",\"Educational\", …"

addedInput schema / properties / confirm_spend_usd

Added value: +{
+  "description": "Explicit approval for an unusually large charge. Calls whose worst case exceeds $5 are refused unless this is set to at least the amount the tool reports. Only set it after the user has agreed to that number.",
+  "type": "number"
+}

addedInput schema / properties / department_headcount

Added value: +{
+  "additionalProperties": false,
+  "description": "Department size, e.g. {\"name\":\"engineering\",\"min\":10,\"max\":100} — realtime only: using it forces the pricier live mode.",
+  "properties": {
+    "max": {
+      "type": "number"
+    },
+    "min": {
+      "type": "number"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name"
+  ],
+  "type": "object"
+}

addedInput schema / properties / exclude_domains

Added value: +{
+  "description": "Exclude companies by domain (e.g. existing customers).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / exclude_ids

Added value: +{
+  "description": "Exclude companies by LinkedIn id/URN.",
+  "items": {
+    "type": [
+      "string",
+      "number"
+    ]
+  },
+  "type": "array"
+}

addedInput schema / properties / exclude_industries

Added value: +{
+  "description": "Industries to exclude.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / exclude_locations

Added value: +{
+  "description": "HQ locations to exclude.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / fallback_from_leads / description

Previous value: -"If no companies, derive from leads by keywords"New value: +"DEPRECATED — accepted but ignored. Removed. It fabricated lead-derived name aggregates and cost an extra billable query."

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

changedInput schema / properties / get_max_companies / description

Previous value: -"Get maximum companies"New value: +"DEPRECATED — accepted but ignored. Always on now: search responses include results_count without asking."

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

addedInput schema / properties / headcount_growth

Added value: +{
+  "additionalProperties": false,
+  "description": "Headcount growth in percent — realtime only: using it forces the pricier live mode.",
+  "properties": {
+    "max": {
+      "type": "number"
+    },
+    "min": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / headcounts / description

Previous value: -"Headcount ranges"New value: +"Size buckets. Allowed ONLY: \"1-10\",\"11-50\",\"51-200\",\"201-500\",\"501-1000\",\"1001-5000\",\"5001-10000\",\"10 000+\"."

addedInput schema / properties / hiring_on_linkedin

Added value: +{
+  "description": "Only companies actively hiring — realtime only: using it forces the pricier live mode.",
+  "type": "boolean"
+}

changedInput schema / properties / industries / description

Previous value: -"Industries"New value: +"Company industries. Must match Generect industry names exactly (e.g. \"Software Development\"); unknown names are rejected with HTTP 400."

changedInput schema / properties / keywords / description

Previous value: -"Keywords"New value: +"Free-text keywords across name/description/specialties — realtime only: using it forces the pricier live mode."

addedInput schema / properties / limit

Added value: +{
+  "description": "Alias for limit_by.",
+  "type": "number"
+}

changedInput schema / properties / limit_by / description

Previous value: -"Number of results to return"New value: +"Rows to return this call (1–100, default 25). You are billed per returned row, so this number IS the price of the call."

addedInput schema / properties / linkedins_links

Added value: +{
+  "description": "Specific LinkedIn company URLs — realtime only: using it forces the pricier live mode.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / locations / description

Previous value: -"Locations (Countries, e.g \"United States\")"New value: +"HQ locations — cities, states or countries."

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 freshness is not critical and cost matters more than freshness.",
+  "enum": [
+    "auto",
+    "database",
+    "realtime"
+  ],
+  "type": "string"
+}

addedInput schema / properties / num_of_followers

Added value: +{
+  "description": "LinkedIn follower buckets: \"1-50\",\"51-100\",\"101-1000\",\"1001-5000\",\"5001+\" — realtime only: using it forces the pricier live mode.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Alias for offset_by.",
+  "type": "number"
+}

changedInput schema / properties / offset_by / description

Previous value: -"Offset for pagination"New value: +"Rows to skip (pagination)."

addedInput schema / properties / revenues_range

Added value: +{
+  "additionalProperties": false,
+  "description": "Annual revenue range, single object {min,max} — realtime only: using it forces the pricier live mode.",
+  "properties": {
+    "max": {
+      "type": "number"
+    },
+    "min": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "min",
+    "max"
+  ],
+  "type": "object"
+}

addedInput schema / properties / sub_industries

Added value: +{
+  "description": "Expand each selected industry to its sub-industries as well (broadens the match).",
+  "type": "boolean"
+}

addedInput schema / properties / technologies

Added value: +{
+  "description": "Technologies the company uses — realtime only: using it forces the pricier live mode.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / timeout_ms / description

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "api_returned_more_than_requested": {
+      "type": "number"
+    },
+    "blocked_by_vocabulary": {
+      "$ref": "#/properties/vocabulary_warnings"
+    },
+    "companies": {
+      "type": "array"
+    },
+    "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"
+    },
+    "escalated_to_realtime_because": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "escalation_note": {
+      "type": "string"
+    },
+    "fix": {
+      "type": "string"
+    },
+    "leads": {
+      "type": "array"
+    },
+    "mode": {
+      "type": "string"
+    },
+    "next_page_args": {},
+    "note": {
+      "type": "string"
+    },
+    "requested_rows": {
+      "type": "number"
+    },
+    "results_count": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "returned": {
+      "type": "number"
+    },
+    "spend_guard": {},
+    "status": {
+      "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.5/5.0

Behavior5/5

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

The description discloses billing per returned row, zero-cost for zero rows, the cost-reading mechanism, snapshot lag for headcount data, and referential guidance to get_balance. The schema adds escalation behavior for auto mode, realtime-only constraints, and HTTP 400 rejections. This goes far beyond the readOnlyHint/openWorldHint annotations without contradicting them.

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 three sentences long, front-loads the core operation, and every sentence carries operational value: what it returns, what it costs, what to run first, and a data-freshness caveat. No filler or repetition of schema content.

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 29-parameter, billable, output-schema-bearing tool, the description plus schema covers cost, prerequisites, mode behavior, data freshness, error conditions, pagination, and deprecations. The output schema handles return-value documentation, so nothing critical is missing for an agent to call this correctly.

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 in detail, including realtime-only behavior and cost implications. The tool-level description adds only a small extra note about headcount snapshot lag, which is useful but not essential given the rich parameter descriptions already present.

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?

The description opens with a specific verb and resource: 'Return companies matching an ICP,' so an agent immediately knows this is a search/list tool for companies. It does not explicitly name a sibling it is not (e.g. count_companies), but 'Return companies' plus the sibling name makes the distinction clear enough.

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 directs the agent to 'Run count_companies first,' providing a concrete sibling-workflow rule. The schema further adds strong mode-selection guidance ('Pick database explicitly when freshness is not critical and cost matters more than freshness') and flags filters that force realtime, which is exactly the kind of when-to-use-vs-alternative guidance this dimension rewards.

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

Deploy Server