Smartlead Simplified MCP Server

smartlead_save_campaign_sequence

Save a multi-step email sequence for a campaign, including delays and variant distribution.

Instructions

Save a sequence of emails for a campaign.

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>",
      "sequence": "<sequence>"
    },
    "name": "smartlead_save_campaign_sequence"
  }
}

Input Schema

Name	Required	Description	Default
`sequence`	Yes	Sequence of emails to send
`campaign_id`	Yes	ID of the campaign

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 18, 2025

TDQS

B3/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Save', but does not explain whether it overwrites the entire sequence, appends, or requires specific permissions. Mutation behavior and side effects are not addressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise but overly minimal; it consists of a single sentence. While it is front-loaded, it lacks critical information necessary for tool selection and usage.

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

Completeness2/5

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

Given the complex nested schema and absence of annotations/output schema, the description is incomplete. It does not cover prerequisites, overwriting behavior, or error conditions, leaving the agent underinformed.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond the schema; parameters are already well-described in the schema. No additional syntax, constraints, or usage tips are provided.

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 that the tool saves a sequence of emails for a campaign, using specific verb 'Save' and concrete objects 'sequence of emails' and 'campaign'. This distinguishes it from sibling tools like smartlead_get_campaign_sequence (retrieve) and smartlead_create_campaign (create campaign).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as whether to use it for initial creation or updates, or any prerequisites like requiring an existing campaign. No explicit context or exclusions are given.

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