Skip to main content
Glama
automatiabcn

leadpipe-mcp

by automatiabcn
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Batch Ingest Leads

lead_batch_ingest
Idempotent

Import up to 100 leads in one batch call. Duplicates are skipped automatically, allowing partial success without failure.

Instructions

Add 1 to 100 leads in a single call. Each lead uses the same schema as lead_ingest. Returns {ingested: Lead[], skipped: Array<{email, reason}>} — duplicates are skipped (not failed) so a partial batch still succeeds. Prefer this over repeated lead_ingest calls for bulk imports (CSV/webhook drops).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leadsYesArray of 1–100 leads, each using the same shape as lead_ingest input. Duplicates within the batch and against existing pipeline emails are SKIPPED (not failed) — partial success is the norm. Returns {ingested: Lead[], skipped: Array<{email, reason}>}.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed12 schema fields changedv1.4.2
    • addedInput schema / properties / leads / description
      Added value: +"Array of 1–100 leads, each using the same shape as lead_ingest input. Duplicates within the batch and against existing pipeline emails are SKIPPED (not failed) — partial success is the norm. Returns {ingested: Lead[], skipped: Array<{email, reason}>}."
    • addedInput schema / properties / leads / items / properties / company_domain / description
      Added value: +"Company root domain (e.g. \"acme.com\"). If omitted, derived from the email. Used by lead_enrich for the domain knowledge-base lookup."
    • addedInput schema / properties / leads / items / properties / company_name / description
      Added value: +"Company display name. If omitted, lead_enrich will derive it from the email domain."
    • addedInput schema / properties / leads / items / properties / custom_fields / description
      Added value: +"Arbitrary string→string metadata. Use for UTM parameters, A/B test variants, or anything you want to preserve through scoring and export."
    • addedInput schema / properties / leads / items / properties / email / description
      Added value: +"Business email address. Required and used as the unique key — duplicate emails are rejected, not upserted. Example: \"alex@acme.com\"."
    • addedInput schema / properties / leads / items / properties / first_name / description
      Added value: +"Optional first name. Stored verbatim and used for personalization in CRM exports."
    • addedInput schema / properties / leads / items / properties / job_title / description
      Added value: +"Job title used by lead_score for the job_title dimension. High-value titles (ceo, cto, vp, director, head, founder) earn the highest points. Configurable via config_scoring.high_value_titles."
    • addedInput schema / properties / leads / items / properties / last_name / description
      Added value: +"Optional last name. Combined with first_name to populate full_name on the stored lead."
    • addedInput schema / properties / leads / items / properties / phone / description
      Added value: +"Optional phone number in any format. Stored verbatim and forwarded to CRM exports."
    • addedInput schema / properties / leads / items / properties / source / description
      Added value: +"Where the lead originated. One of: website_form, landing_page, api, csv_import, manual, webhook. Defaults to \"api\"."
    • addedInput schema / properties / leads / items / properties / source_detail / description
      Added value: +"Free-text refinement of source — e.g. \"homepage hero form\", \"Q1 webinar\", \"Reddit r/SaaS post\"."
    • addedInput schema / properties / leads / items / properties / tags / description
      Added value: +"Free-form tags for downstream filtering in lead_search and lead_export. Example: [\"enterprise\", \"follow_up\", \"demo_requested\"]."
  2. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Discloses that duplicates are skipped (not failed) so partial batches succeed, and specifies the return structure with ingested and skipped arrays. This adds significant detail beyond annotations, which only indicate idempotency and non-destructiveness.

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?

Three sentences, all essential: action and limits, behavior on duplicates, and usage guidance. Front-loaded with core purpose.

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?

Given the single parameter and no output schema, the description covers all important aspects: batch size, duplicate handling, return format, and comparison to sibling tool. Nothing missing.

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

Parameters4/5

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

Schema coverage is 100% with detailed property descriptions. The description adds the response shape and references the sibling tool's schema, which is helpful since no output schema is provided. Baseline is 3, but the added output semantics justify a 4.

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 clearly states 'Add 1 to 100 leads in a single call,' specifying the action and resource. It distinguishes from sibling tool lead_ingest by mentioning bulk imports and directs users to prefer this over repeated calls.

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?

Explicitly advises 'Prefer this over repeated lead_ingest calls for bulk imports (CSV/webhook drops),' giving clear context on when to use this tool and when to use the alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/automatiabcn/leadpipe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server