Generect Live API MCP Server

Official

Overview Schema Source Related Servers Discussions(1)Admin

Find a phone number (most expensive)

find_phone

Retrieve a phone number for one qualified person using a lead ID, LinkedIn URL, or name and company. Billable per phone found, so confirm with the user before calling.

Instructions

Find a phone number for one person. BILLABLE — about $0.4 per phone found (a miss is free) (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). THE MOST EXPENSIVE OPERATION HERE — roughly 20x an email lookup. Do not call it speculatively or across a list; confirm with the user first, and only for people they have already qualified. Use start_bulk_job for an approved list.

Input Schema

TableJSON Schema

Name	Required	Description
`domain`	No	Company domain without protocol, e.g. "stripe.com" (name+domain mode).
`company`	No	Company name or domain (name+company mode).
`lead_id`	No	Generect lead id from search / preview / enrich results — the cheapest and most accurate identifier.
`last_name`	No	Last name (name+domain mode).
`first_name`	No	First name (name+domain mode).
`timeout_ms`	No	Request timeout in milliseconds.
`linkedin_url`	No	LinkedIn profile URL.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cost`	No
`result`	No
`test_mode`	No
`test_mode_notice`	No
`vocabulary_warnings`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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
```

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: +{}
```

Addedv0.9.0Sep 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: billable at ~$0.4 per hit, misses free, ~20x an email lookup, tiered pricing that may differ, and the cost.amount_charged field and get_balance route for real spend. This is exactly the cost/auth-style disclosure annotations cannot carry.

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?

Front-loads the action and the cost warning, and every sentence carries useful information. The nested parentheticals about tiered pricing and cost.amount_charged make one sentence dense, but nothing is truly wasteful.

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?

With annotations covering the safety profile and an output schema covering returns, the description still supplies the pricing, confirmation-before-calling, and alternative-tool context an agent needs. Nothing material 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 all seven parameters are already documented in the schema (domain, lead_id, first/last name, linkedin_url, etc.). The description adds no parameter-level meaning, which is acceptable at full coverage but not value-adding.

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 and resource ('Find a phone number for one person') and explicitly scopes it to a single individual, which separates it from bulk and email siblings. An agent can identify the operation immediately without reading 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('only for people they have already qualified'), when-not ('Do not call it speculatively or across a list'), and names the alternative for approved lists (start_bulk_job). Routing guidance is unambiguous.

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

Deploy Server