Generect Live API MCP Server

Official

by generect

Overview Schema Source Related Servers Discussions(1)Admin

TypeScript

Hybrid

Count matching companies (free)

count_companies

Read-onlyIdempotent

Count companies matching your ICP filters for free before searching, with optional realtime counts billed at $0.02 each.

Instructions

How many companies match an ICP, and what pulling them would cost. FREE — this call never spends credits. Call this before search_companies. As with count_leads, a realtime count costs $0.02 and is never run implicitly.

Input Schema

TableJSON Schema

Name	Required	Description
`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 you only need a size estimate and cost matters more than freshness.
`keywords`	No	Free-text keywords across name/description/specialties — realtime only: using it forces the pricier live mode.
`locations`	No	HQ locations — cities, states or countries.
`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.
`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
`why`	No
`cost`	No
`mode`	No
`advice`	No
`status`	No
`options`	No
`test_mode`	No
`results_count`	No
`needs_realtime`	No
`test_mode_notice`	No
`next_step_estimate`	No
`vocabulary_warnings`	No
`blocked_by_vocabulary`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 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 / department_headcount / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / headcount_growth / 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 you only need a size estimate 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 you only need a size estimate and cost matters more than freshness."

removedInput schema / properties / revenues_range / 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"

removedOutput schema / properties / blocked_by_vocabulary / $ref
```
Removed value: -"#/properties/vocabulary_warnings"
```
addedOutput schema / properties / blocked_by_vocabulary / items
```
Added value: +{}
```
addedOutput schema / properties / blocked_by_vocabulary / type
```
Added value: +"array"
```
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.2/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld), but the description adds non-obvious billing semantics: the call is free, a realtime count costs $0.02, and it is 'never run implicitly' — real behavioral context an agent could not infer from annotations alone. It stops short of noting latency for realtime counts or how cost is reported.

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?

Three short sentences, front-loaded with what the tool returns and what it costs, with no filler. Every clause 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?

With an output schema present, return values need no explanation, and the description correctly focuses on the cost/credit model that the schema cannot express. Coverage is nearly complete; only the difference from sibling preview/count tools is left implicit.

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% and the 23 parameters are richly documented (mode enums, per-field 'realtime only' cost warnings, deprecated fields), so the description's minimal parameter commentary is acceptable. The only added hint is cost-related, which is already implied by the mode field.

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 ('count companies matching an ICP') plus an adjacent deliverable ('what pulling them would cost'), which clearly separates it from search_companies (retrieval) and count_leads (a different resource).

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?

Gives a strong explicit ordering directive ('Call this before search_companies') and implies the pre-flight-estimate use case, but never states when this tool is NOT the right choice or how it differs from preview_leads.

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

Deploy Server