Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Save campaign sequence

save_campaign_sequence
Idempotent

Save or replace a campaign's main sequence of day-by-day email and LinkedIn steps, updating the Messaging tab plan without enrolling contacts or sending messages.

Instructions

Saves a campaign's main sequence: the emails (and any LinkedIn steps) every enrolled person gets, on their days, as on the campaign's Messaging tab. steps replaces the saved sequence; a connection request with no emails makes the campaign LinkedIn-only. Saves only: nothing is enrolled or sent. A campaign already sending uses the new wording on its live emails; changing the number or days of steps needs sending paused. 409 means the sequence changed since revision was read. Returns the same shape as get_campaign_email.

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>",
      "steps": "<steps>"
    },
    "name": "save_campaign_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsYesThe whole sequence in order, with at least one email or a LinkedIn connection request. A sequence with a connection request and no emails is LinkedIn-only: it sends no email and needs no mailbox. It replaces the saved sequence.
revisionNoThe sequence.revision the edit was based on. When omitted, whatever is saved now is replaced.
campaign_idYes

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?

Beyond the annotations, it discloses replace-not-merge semantics for steps, the LinkedIn-only edge case (a connection request with no emails needs no mailbox), the live-campaign effect on already-sending emails, the paused requirement for step count/day changes, and the meaning of a 409 as a revision conflict. There is mild tension with destructiveHint=false since the sequence is overwritten, but the replace behavior is stated openly rather than hidden, so the agent is not misled.

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 most important fact, that steps replaces the saved sequence, is front-loaded, and each subsequent sentence carries distinct information (side effects, LinkedIn-only case, pause requirement, conflict code, return shape). It is dense but nearly every clause earns its place, with only slight compression cost in readability.

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 side effects, preconditions, concurrency conflict handling, and the return value ("same shape as get_campaign_email"). An agent has enough to call it correctly and interpret the response without further discovery.

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?

The schema already documents most fields at 67% coverage, but the description adds meaning the schema does not: that steps is a whole-sequence replacement rather than an append, and that an omitted revision means whatever is saved now gets replaced while a 409 signals the sequence moved since revision was read. That directly clarifies the two required/optional parameters beyond their field-level text.

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 plus scope: "Saves a campaign's main sequence: the emails (and any LinkedIn steps) every enrolled person gets, on their days." It distinguishes the write from the read siblings by referencing the Messaging tab and the replacement of the saved sequence, so an agent knows this persists a sequence rather than retrieving one.

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 clearly bounds the tool's effect ("Saves only: nothing is enrolled or sent") and states the precondition for structural edits ("changing the number or days of steps needs sending paused"). What it lacks is explicit routing to the alternatives for enrollment or activation, leaving the agent to infer those from the scope statement.

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