Skip to main content
Glama

lemlist_push_rows

Create lemlist leads FROM DATASTORE ROWS — the bulk way; nothing personal goes through this call.

Name the rows (row_ids, or a filter); oto reads them, creates one lead per row in the campaign, and writes back id_column (the lead id) and status_column (pushed | duplicate | failed) on each row. The answer is counts plus errors: [{row_id, code}] — never a value read from a row.

By filter, only rows whose status_column is empty are taken: call again with the same filter until remaining is 0. A row already treated is not picked again — name it in row_ids to retry it. A row with id_column already set is skipped (already_pushed); one reserved by another run is skipped (row_locked) before anything is sent. dry_run reads and checks the mapping, sends nothing. Like lemlist_create_lead, this sends no email: a lead waits for review until lemlist_launch_lead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "datastore": "<datastore>",
      "campaign_id": "<campaign_id>",
      "field_mapping": "<field_mapping>"
    },
    "name": "lemlist_push_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
filterNodata_rows filter grammar; `{}` = every row not yet treated.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
dry_runNoread and check only — no lemlist call, nothing written.
row_idsNothe rows to push (at most 50). Exclusive with `filter`.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
datastoreYesthe table, by name or number.
id_columnNowhere the lemlist lead id is written back.lemlist_lead_id
batch_sizeNorows per call with `filter` (1-50).
campaign_idYeslemlist campaign id WITH its `cam_` prefix.
deduplicateNoskip a lead whose email is already in another campaign.
field_mappingYes{lead field: column}. Lead fields are those of lemlist_create_lead (email, first_name, last_name, company_name, job_title, linkedin_url, phone, company_domain, icebreaker, timezone, contact_owner); any other key becomes a custom variable. A row needs an email, a linkedin_url or a phone.
status_columnNowhere pushed | duplicate | failed is written back; the code of a duplicate or a failure goes in its `comment` layer.lemlist_status

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations the description carries the full load, and it does most of it: side effects (writes id_column and status_column per row), skip conditions (already_pushed, row_locked before anything is sent), return shape (counts plus errors: [{row_id, code}]), and the no-email-sent guarantee. It stops short of permission/auth requirements or rate-limit behavior.

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 purpose, then mechanics, then the sibling relationship; nearly every sentence earns its place. Slightly dense with parenthetical asides and backticked identifiers, but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter bulk mutation with no output schema, the description covers selection, write-back, idempotency, error reporting, and the downstream review gate. The remaining gap is the _org/_group/_project/_run_id scoping parameters, which are left entirely to the schema.

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%, so baseline is 3, but the description adds real meaning the schema does not: filter only takes rows whose status_column is empty, row_ids is the retry path for an already-treated row, and id_column/status_column are write-back targets rather than inputs. field_mapping and batch_size get no extra treatment beyond the schema.

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 a specific verb+resource ('Create lemlist leads FROM DATASTORE ROWS') and immediately frames its scope as the bulk path versus the single-lead sibling, explicitly naming lemlist_create_lead and lemlist_launch_lead.

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?

Gives explicit when-to-use routing: row_ids vs filter are described as alternatives, the filter loop ('call again with the same filter until remaining is 0') is spelled out, retry via row_ids is prescribed, and dry_run is positioned as the pre-check. Alternatives are named, not implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources