Tulina

lemlist_mailbox

Mailboxes: connect/disconnect/test, and lemwarm (deliverability warm-up).

Args by op:

connect: smtp_imap — one dict carrying sender_name, sender_email, smtp_host, smtp_port, smtp_login, smtp_password, imap_host, imap_port, imap_login, imap_password (all required), plus smtp_secure, imap_secure, user_id. ⚠️ MAILBOX CREDENTIALS travel here.
disconnect / test: email_account_id. Disconnecting stops the campaigns sending from it.
lemwarm / lemwarm_update (settings: warmEmailMax, warmEmailRampup, answerPercentage…) / lemwarm_start / lemwarm_pause: mailbox_id.

lemwarm_start DOES send — inside the warm-up network (other lemlist mailboxes), never to a prospect. That is why it sits in a visible tool while the prospect-facing sends do not.

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": {
      "op": "<op>"
    },
    "name": "lemlist_mailbox"
  }
}

Input Schema

Name	Required	Description
`op`	Yes
`_org`	No	Org (id) de CET APPEL. `oto_list_orgs()`.
`_group`	No	Équipe (id) de CET APPEL, sous son org parente.
`_run_id`	No	OBLIGATOIRE à 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.
`_project`	No	Projet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
`settings`	No
`_instance`	No	Instance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
`smtp_imap`	No
`mailbox_id`	No
`email_account_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it flags that mailbox credentials travel inside `smtp_imap`, that `disconnect` has the side effect of halting campaigns, and that `lemwarm_start` actually sends mail but only within the warm-up network. It stops short of stating permission/auth requirements, reversibility of a disconnect, or what `test` verifies, so it is strong but not exhaustive.

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 one-line scope summary followed by a tight bullet-per-op mapping; every bullet maps an op to its inputs rather than restating the name. Slightly padded by the closing remark explaining why this visible tool may send while prospect-facing sends may not, and by the ellipsis in the settings list.

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 ten-parameter, seven-way dispatcher with no annotations and no output schema, the description covers every op and its inputs plus the two dangerous behaviors (credential handling, campaign-stopping disconnect). Return values for `test` and the read-style `lemwarm` are unaddressed, which is the remaining gap.

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 only 50% and the key objects (`smtp_imap`, `settings`, `mailbox_id`, `email_account_id`) have no schema descriptions, yet the description enumerates the ten required SMTP/IMAP keys, names the optional `smtp_secure`/`imap_secure`/`user_id`, and maps `settings` to warmEmailMax, warmEmailRampup, answerPercentage. The '…' elision leaves the rest of `settings` unspecified, and the framework params are left to 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?

The first line names the resource (mailboxes) and enumerates the concrete operations: connect/disconnect/test plus lemwarm warm-up. The per-op section then disambiguates each of the seven enum values with its own verb-resource pairing, so an agent knows exactly what each `op` branch does without opening the schema.

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?

Guidance is organized by operation ('Args by op') and includes the key selection context: disconnecting 'stops the campaigns sending from it', and lemwarm_start sends only inside the warm-up network, never to a prospect. It does not route the agent away from overlapping siblings such as lemlist_deliverability or mailpool_mailboxes, and gives no prerequisites or ordering advice, which keeps it short of a 5.

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

All Tulina tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?