ExtractorLead MCP Server

Lanzar enriquecimiento masivo

start_bulk_enrichment

Starts bulk lead enrichment for a list of people or CSV/XLSX file, consuming credits only after preview and user confirmation, and returns a task ID to track progress.

Instructions

Lanza el enriquecimiento de una lista de personas. Consume créditos.

Solo tras preview_bulk_enrichment y con la confirmación del usuario.
Devuelve un task_id; sigue el trabajo con get_bulk_status.

Entrada (una de las dos):
- leads: lista de filas, cada una con los campos que tenga: first_name,
  last_name, full_name, company, domain, title, linkedin_url, email,
  location. También valen cabeceras en español (Nombre, Apellido, Cargo,
  Empresa, LinkedIn...). Máx. 5000 filas.
- file_path: ruta a un CSV/XLSX local (solo servidor local; un export de
  Sales Navigator vale tal cual).
Opciones:
- contact_info: "all_contact_info" (por defecto: pide el teléfono y entrega
  el email solo de quien tiene teléfono), "phone_info" o "email_info".
- match_mode: "strict" (la persona exacta) o "related" (además otros
  contactos análogos de la misma empresa, usando el cargo como semilla).
- related_per_company: 1..10 contactos análogos por empresa (con related).
- require_mobile: true para contar solo móviles, no centralitas.
Precio por contacto ENTREGADO: solo email 2, solo teléfono 3, ambos 4,
nada 0 créditos.

Input Schema

Name	Required	Default
`leads`	No
`file_path`	No
`match_mode`	No	strict
`contact_info`	No	all_contact_info
`require_mobile`	No
`related_per_company`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 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 annotations: credits are consumed, per-contact pricing for delivered data, the 5000-row cap, and the constraint that file_path only works on a local server. Annotations declare non-read-only and non-idempotent, and the description is consistent with that while explaining real consequences.

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?

Front-loads cost before anything else, then the precondition, then inputs and options in short labeled blocks. The pricing line is terse and high-value rather than filler.

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?

An output schema exists so return values need not be spelled out, yet the description still names task_id and the status tool for polling. With the credit model, row cap, input shape and enum semantics all covered, nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and does: it enumerates accepted lead fields (including Spanish headers), the one-of leads/file_path input rule, the exact meaning and default behavior of each contact_info enum value, strict vs related match semantics, the 1..10 range for related_per_company, and require_mobile.

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 concrete verb+resource ('Lanza el enriquecimiento de una lista de personas') and immediately signals cost and the returned task_id, which differentiates it from preview_bulk_enrichment and get_bulk_status. It never distinguishes itself from the sibling start_list_enrichment, so an agent given a saved list cannot tell which launcher applies.

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?

Explicit precondition: only after preview_bulk_enrichment and with user confirmation, which is a real gate most definitions omit. It also routes follow-up to get_bulk_status. The exclusion is incomplete in that start_list_enrichment/preview_list_enrichment are never named as the alternative path.

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

Deploy Server