Mobile Phone Waterfall MCP Server

Find mobile phone

find_mobile_phone

Read-only

Find a mobile number for each contact by querying your Prospeo, Lusha, ContactOut, and FullEnrich accounts in order until one returns a number. Returns E.164 results with line type and credits.

Instructions

Find a mobile phone number for each contact by calling the buyer's own phone data providers in order (Prospeo, Lusha, ContactOut, FullEnrich) until one returns a number. Returns one row per contact with the number in E.164 format, its line type, country, a Do Not Call flag where the provider reports one, the provider that found it, and the provider credits it spent, plus a run summary row. Provider keys are read from the PROSPEO_API_KEY, LUSHA_API_KEY, CONTACTOUT_API_KEY, and FULLENRICH_API_KEY environment variables of this server; with none set, the run completes, calls nothing, and charges nothing. A LinkedIn URL is passed to providers as an identifier and never opened. A run that does not succeed is returned as an error with its run ID. Requires an APIFY_TOKEN and consumes Apify credits per contact searched and per number found, plus the buyer's own provider credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_mobile_phone"
  }
}

Input Schema

Name	Required	Description
`email`	No	Single contact shortcut: email.
`contacts`	No	People to look up. Give each as many identifiers as you hold.
`full_name`	No	Single contact shortcut: full name.
`mobile_only`	No	When true, a landline or VoIP number does not count as found and the chain moves on. Numbers with no reported line type are kept as unknown. Default true.
`linkedin_url`	No	Single contact shortcut: LinkedIn profile URL, never opened by the actor.
`max_contacts`	No	Ceiling on how many contacts this run processes.
`company_domain`	No	Single contact shortcut: company domain.
`max_charge_usd`	No	Optional cap on this run's Apify charges. The run stops before a charge that would pass it and keeps every row already paid for.
`provider_order`	No	Providers in call order. Default prospeo, lusha, contactout, fullenrich. A provider with no key is skipped and reported.
`max_provider_credits`	No	Cap on the provider credits this run may spend on the buyer's own accounts. Remaining contacts are skipped, uncharged. Strongly recommended.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations cover only the read/write and world-openness profile; the description adds the expensive details an agent needs: Apify credits plus the buyer's own provider credits, required APIFY_TOKEN, provider keys read from named environment variables, Do Not Call flag handling, and that a failed run is returned as an error with its run ID. LinkedIn URLs are explicitly never opened.

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?

The return shape and cost profile are front-loaded, then auth, then failure behavior — a sensible ordering. It is long and runs several clauses per sentence, but almost every clause carries information an agent needs before calling.

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 no output schema, the description fully carries the return contract: one row per contact with E.164 number, line type, country, DNC flag, provider, credits spent, plus a run summary row. Cost, auth and failure semantics are all present, so 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 coverage is 100%, so parameter documentation is already complete, including the mobile_only default and provider_order default. The description mostly restates those defaults rather than adding new parameter-level meaning, so the baseline 3 applies.

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 names a specific verb and resource ('Find a mobile phone number for each contact') and goes further to explain the mechanism: a sequential waterfall across Prospeo, Lusha, ContactOut and FullEnrich. An agent knows exactly what the tool produces without opening 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 Guidelines4/5

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

It gives clear operating context — the provider chain stops at the first hit, providers without keys are skipped, and with no keys set the run completes and charges nothing. There are no sibling tools to route against, so no exclusions are needed, but it also never states when this tool is the wrong choice.

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

Deploy Server

Other Tools

find_mobile_phoneA