ExtractorLead MCP Server

Cotizar enriquecimiento masivo

preview_bulk_enrichment

Read-only

Validate a lead list and calculate maximum enrichment cost without charging, showing accepted rows, max credits, and available credits before bulk enrichment.

Instructions

Valida una lista de personas y calcula el coste máximo. NO cobra nada.

Úsalo SIEMPRE antes de start_bulk_enrichment y enseña al usuario
rows_accepted, max_credits y available_credits.

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.9/5.0

Behavior5/5

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

Annotations already flag readOnlyHint/openWorldHint, and the description adds genuinely new behavioral facts: no credits are charged, hard cap of 5000 rows, file_path only works on a local server, and a per-delivered-contact price table (2/3/4/0 credits). That pricing and capacity context is exactly what an agent needs and cannot get from the schema.

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-loaded with the no-charge guarantee and the ordering rule, then organized into clearly labeled blocks (Entrada / Opciones / Precio). It runs long, but nearly every line adds operational value; only the pricing sentence could be trimmed slightly.

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, yet the description still names the key return fields to show the user, and it covers input formats, limits, pricing, and the hand-off to start_bulk_enrichment. Nothing an agent needs to invoke this 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 and Spanish header aliases, explains file_path formats (CSV/XLSX, Sales Navigator export), and defines each enum value's business meaning (all_contact_info vs phone_info vs email_info, strict vs related) plus the 1..10 range for related_per_company.

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 specific verbs (validate a list, compute max cost) plus the crucial scope caveat that nothing is charged, and explicitly contrasts with start_bulk_enrichment. An agent can immediately tell this is the dry-run/quote step of a two-step bulk flow.

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?

'Úsalo SIEMPRE antes de start_bulk_enrichment' gives an explicit ordering rule naming the alternative, and it also tells the agent what to surface to the user (rows_accepted, max_credits, available_credits). No inference required about when to call it.

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

Deploy Server