Skip to main content
Glama
generect

Generect Live API MCP Server

Official
by generect

Search companies (free thin rows, full rows billed)

search_companies

Find companies matching your ideal customer profile by industry, size, location, and type. Count results free first, then browse free thin rows before paying to enrich only the ones you keep.

Instructions

Return companies matching an ICP. Free by default while the account has free thin rows left today (a daily quota; detail "thin" guarantees $0). Thin rows carry no domain; enrich_company adds it for the ones you keep. detail "full" is billable: about $0.02 per returned row (0 rows costs $0) 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. Realtime is billed per row too. count_companies sizes the result for free first. 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

NameRequiredDescriptionDefault
modeNoData 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 freshness is not critical and cost matters more than freshness.
limitNoAlias for limit_by.
detailNoRow detail for the database search. Thin rows are FREE — id, name, industry, headcount_range, HQ country/city, company_type, founded_year; no LinkedIn URL, domain, contacts or history — up to a daily per-account row quota that resets at 00:00 UTC. Omitted (default): thin while the free tier is available; once it is not (quota spent, a custom-contract account, a server without the tier) the search continues as before — full rows billed per row, marked thin_unavailable in the result, under the spend ceiling. "thin": free rows only — never billed, never escalated to realtime; a spent quota is a 429 and a realtime-only filter is an error. "full": the whole record, billed per row. Browse thin, then spend only on the rows you keep: generate_email takes the lead id directly, enrich_* gives the full record.
offsetNoAlias for offset_by.
compactNoDefault 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.
keywordsNoFree-text keywords across name/description/specialties — realtime only: using it forces the pricier live mode.
limit_byNoRows to return this call (1–100, default 25). You are billed per returned row, so this number IS the price of the call.
locationsNoHQ locations — cities, states or countries.
offset_byNoRows to skip (pagination).
headcountsNoSize buckets. Allowed ONLY: "1-10","11-50","51-200","201-500","501-1000","1001-5000","5001-10000","10 000+".
industriesNoCompany industries. Must match Generect industry names exactly (e.g. "Software Development"); unknown names are rejected with HTTP 400.
timeout_msNoRequest timeout in milliseconds.
exclude_idsNoExclude companies by LinkedIn id/URN.
technologiesNoTechnologies the company uses — realtime only: using it forces the pricier live mode.
company_namesNoRestrict to specific company names — realtime only: using it forces the pricier live mode.
company_typesNoCompany types: "Public Company","Privately Held","Non Profit","Government Agency","Educational", …
revenues_rangeNoAnnual revenue range, single object {min,max} — realtime only: using it forces the pricier live mode.
sub_industriesNoExpand each selected industry to its sub-industries as well (broadens the match).
exclude_domainsNoExclude companies by domain (e.g. existing customers).
linkedins_linksNoSpecific LinkedIn company URLs — realtime only: using it forces the pricier live mode.
headcount_growthNoHeadcount growth in percent — realtime only: using it forces the pricier live mode.
num_of_followersNoLinkedIn follower buckets: "1-50","51-100","101-1000","1001-5000","5001+" — realtime only: using it forces the pricier live mode.
confirm_spend_usdNoExplicit 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_locationsNoHQ locations to exclude.
get_max_companiesNoDEPRECATED — accepted but ignored. Always on now: search responses include results_count without asking.
exclude_industriesNoIndustries to exclude.
hiring_on_linkedinNoOnly companies actively hiring — realtime only: using it forces the pricier live mode.
fallback_from_leadsNoDEPRECATED — accepted but ignored. Removed. It fabricated lead-derived name aggregates and cost an extra billable query.
department_headcountNoDepartment size, e.g. {"name":"engineering","min":10,"max":100} — realtime only: using it forces the pricier live mode.
allow_unlisted_valuesNoEscape hatch for the local vocabulary check — see the lead-side field of the same name.

Output Schema

NameRequiredDescriptionDefault
fixNo
costNo
modeNo
noteNo
leadsNo
detailNo
statusNo
returnedNo
companiesNo
free_tierNo
test_modeNo
thin_noteNo
spend_guardNo
results_countNo
next_page_argsNo
requested_rowsNo
escalation_noteNo
test_mode_noticeNo
thin_unavailableNo
vocabulary_warningsNo
blocked_by_vocabularyNo
deprecated_params_ignoredNo
escalated_to_realtime_becauseNo
api_returned_more_than_requestedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.12.3
    • addedOutput schema / properties / detail
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / free_tier
      Added value: +{}
    • addedOutput schema / properties / thin_note
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / thin_unavailable
      Added value: +{
      +  "type": "string"
      +}
  2. Changed15 schema fields changedv0.12.2
    • 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
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Row detail for the database search. Thin rows are FREE — id, name, industry, headcount_range, HQ country/city, company_type, founded_year; no LinkedIn URL, domain, contacts or history — up to a daily per-account row quota that resets at 00:00 UTC. Omitted (default): thin while the free tier is available; once it is not (quota spent, a custom-contract account, a server without the tier) the search continues as before — full rows billed per row, marked thin_unavailable in the result, under the spend ceiling. \"thin\": free rows only — never billed, never escalated to realtime; a spent quota is a 429 and a realtime-only filter is an error. \"full\": the whole record, billed per row. Browse thin, then spend only on the rows you keep: generate_email takes the lead id directly, enrich_* gives the full record.",
      +  "enum": [
      +    "thin",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • 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 freshness is not critical 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 freshness is not critical 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 / companies / items
      Added value: +{}
    • addedOutput schema / properties / deprecated_params_ignored / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / leads / items
      Added value: +{}
    • addedOutput schema / properties / vocabulary_warnings / items
      Added value: +{}
  3. Changed32 schema fields changedv0.9.0
    • 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"
      +}
  4. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the daily free-row quota and its 00:00 UTC reset, exact full-row price (~$0.02), the $0-for-zero-rows rule, where the actual charge is reported (cost.amount_charged_usd), what thin rows omit (no domain), and that headcount_range is an indexing-time snapshot that can lag. This is precisely the billing and data-quality context an agent needs before spending.

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?

Five sentences, cost model front-loaded and no filler. Dense but each sentence carries pricing, quota or data-quality information; the headcount-range caveat at the end is slightly buried for an operational warning.

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?

Output schema exists, so return values needn't be explained, and the description fully covers the cost/quota/detail dimensions that matter most for a 30-parameter billable search. The mode/auto-escalation and spend-ceiling behavior are left entirely to the schema, which is acceptable but means the description alone wouldn't tell an agent how mode selection interacts with the billing story.

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 coverage is 100% and the detail enum already documents thin vs full at length, so the description largely restates it. It does add two things not in the schema: thin rows lack domains and enrich_company fills them, and headcount_range is applied at query time despite being an indexed snapshot — but this is marginal against an already-exhaustive 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+resource ("Return companies matching an ICP") and immediately frames the cost/detail model that distinguishes it. Sibling differentiation is partial — count_companies is named as the free sizing step, but search_leads/enrich_company are only referenced in passing rather than contrasted.

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 actionable routing: "count_companies sizes the result for free first" and "Browse thin, then spend only on the rows you keep," which names the cheaper alternative and the pay-only-for-what-you-keep pattern. No explicit when-not-to-use clause, and the database-vs-realtime choice lives in the schema rather than the description.

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