ExtractorLead MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXTRACTORLEAD_API_KEY | Yes | Your ExtractorLead API key (starts with sk_live_). Required for the local stdio server. For the remote HTTP connector, supply the key via the X-API-Key header, an Authorization: Bearer header, or an api_key query parameter instead. | |
| EXTRACTORLEAD_API_URL | No | Overrides the ExtractorLead API base URL (default https://api.extractorlead.com). | https://api.extractorlead.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountA | Saldo de créditos y estado de la suscripción de ExtractorLead. Úsalo antes de lanzar cualquier trabajo para saber si hay saldo suficiente. |
| search_leadsA | Busca leads nuevos de un nicho en una zona. Consume créditos.
Devuelve un task_id; recoge los leads con get_task_result. Pide confirmación al usuario antes de llamarla. |
| lookup_linkedin_profileA | Obtiene email, teléfono y datos profesionales de UN perfil de LinkedIn. linkedin_url: https://www.linkedin.com/in// Devuelve un task_id; el resultado se recoge con get_task_result. |
| analyze_websiteA | Analiza una web: contactos (emails, teléfonos, redes), negocio y servicios. url debe incluir http:// o https://. Devuelve un task_id para get_task_result. |
| get_task_resultA | Estado y resultado de search_leads, lookup_linkedin_profile o analyze_website.
|
| preview_bulk_enrichmentA | Valida una lista de personas y calcula el coste máximo. NO cobra nada. |
| start_bulk_enrichmentA | Lanza el enriquecimiento de una lista de personas. Consume créditos. |
| get_bulk_statusA | Contadores de un trabajo masivo (nunca la lista). phase: processing | awaiting_phones | completed. Con partial=true ya se pueden leer los leads decididos con get_bulk_results. Los teléfonos pueden tardar hasta ~1 hora: si phase es awaiting_phones, avisa al usuario y vuelve a consultar más tarde en lugar de esperar en bucle. |
| get_bulk_resultsB | Leads enriquecidos de un trabajo masivo, paginados (per_page máx. 200). Para listas grandes ofrece al usuario get_bulk_download_link en vez de paginar todo en la conversación. |
| get_bulk_download_linkA | Enlace temporal (15 min) para descargar todos los leads del trabajo en JSON. |
| preview_list_enrichmentA | Analiza una lista propia (CRM, Excel) y cotiza rellenar sus huecos. NO cobra. A diferencia del enriquecimiento masivo, conserva las columnas del usuario y devuelve su mismo Excel con columnas nuevas. Devuelve columnas detectadas, huecos (sin_telefono, sin_email...), coste y tope_sugerido.
|
| start_list_enrichmentB | Lanza el relleno de huecos de una lista. Consume créditos hasta credit_cap. credit_cap: tope de gasto que el usuario ha aprobado (usa el tope_sugerido de preview_list_enrichment si no dice otro). Sigue el trabajo con get_list_enrichment. |
| get_list_enrichmentB | Estado del relleno de lista; al terminar, resumen y enlace al Excel editado. include_rows=true añade las filas (paginadas con offset/limit, máx. 200). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| prospect | Plantilla para buscar leads de un nicho con confirmación de coste. |
| enrich_my_list | Plantilla para enriquecer una lista de contactos propia. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools are clearly distinct (account, search, single-profile lookup, website analysis), but the surface contains two parallel pipelines that are easy to conflate: preview_bulk_enrichment/start_bulk_enrichment/get_bulk_status/get_bulk_results versus preview_list_enrichment/start_list_enrichment/get_list_enrichment. The descriptions do explain the difference (bulk = discover contacts from a person list, list = fill gaps preserving user columns), but an agent must read carefully to pick correctly. Polling is also split across three different mechanisms (get_task_result, get_bulk_status/results, get_list_enrichment), which adds a second layer of selection risk.
Every tool follows a consistent snake_case verb_noun pattern (get_account, search_leads, preview_bulk_enrichment, start_bulk_enrichment, get_bulk_results, get_list_enrichment). The bulk/list prefixes create a predictable family structure, and the preview_/start_/get_ prefixes signal lifecycle stage clearly.
13 tools is well within the well-scoped 3-15 range. Each tool maps to a real step of the two enrichment workflows plus the lead-search workflow, and none appear redundant at the surface level.
Coverage is strong: credits/account, lead search, single-profile lookup, website analysis, task polling, and full preview/start/status/results/download lifecycles for both bulk and list enrichment. Minor gaps remain — there is no cancellation tool despite a CANCELLED status being exposed, and no task/job history listing, though agents can work around both.