Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Start campaign sending

start_campaign_sending

Activates a campaign to send real prospect outreach via email or LinkedIn, requiring a two-step confirmation to prevent accidental sends.

Instructions

Switches a campaign's sending on: enrolled people start getting its sequence from the account's mailboxes on its sending days and hours. This emails real prospects. A LinkedIn-only sequence (no emails) sends no email and needs no mailbox: it contacts real prospects from the connected LinkedIn account instead. The first call sends nothing and returns needs_confirmation, will_happen (the sequence, how many people, which mailboxes and days, or the LinkedIn account) and confirmation; sending starts only on a second call with the same campaign_id and that confirmation. A 400 error names what is missing (sequence, mailbox, LinkedIn account or enrolled people). Returns the get_campaign_email shape with sending true.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "start_campaign_sending"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYes
confirmationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, but the description adds the crucial real-world consequence: 'This emails real prospects' and, for LinkedIn-only sequences, contacts real prospects via the connected LinkedIn account. It discloses the dry-run-first confirmation gate, what will_happen contains, and what a 400 error reports — behavior an agent cannot infer from annotations.

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?

The key action and the confirmation-gate are front-loaded, and the LinkedIn-only caveat and error/return notes follow logically. It is fairly dense and slightly long, but nearly every sentence carries operational value; the closing note about the get_campaign_email return shape is compact and useful.

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?

For a mutation tool with no output schema, the description covers the essential gaps: the side effect (real emails/LinkedIn contact), the mandatory confirmation handshake, error signaling, and the return shape ('get_campaign_email shape with sending true'). An agent has everything needed to call it safely and interpret the result.

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?

With schema description coverage reported at 0%, the description compensates well: it explains that the second call must use 'the same campaign_id' and 'that confirmation' value returned by the first call, and when to omit confirmation. The confirmation mechanics are largely stated in the schema itself, so the added meaning is solid but not exhaustive (e.g., no detail on campaign_id validity beyond exclusiveMinimum).

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 opens with a specific verb and resource: 'Switches a campaign's sending on', and immediately clarifies the scope (enrolled people receiving the sequence from the account's mailboxes on configured days/hours). It also carves out a distinct mode (LinkedIn-only sequences) so an agent can tell exactly what this tool enables versus pause_campaign_sending.

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?

It gives a clear two-step protocol: the first call sends nothing and returns needs_confirmation/will_happen/confirmation, and sending starts only on a second call with the same campaign_id plus that confirmation. It also explains the 400 error case. It does not explicitly name the sibling to use for stopping sending (pause_campaign_sending), so it stops just short of full alternative routing.

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

Deploy Server

Other Tools