Smartlead Simplified MCP Server

smartlead_add_lead_to_campaign

Add a lead to a Smartlead campaign using the campaign ID and email. Optionally include phone, name, company, and custom fields to enrich the lead.

Instructions

Add a new lead to 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>",
      "email": "<email>"
    },
    "name": "smartlead_add_lead_to_campaign"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Email address of the lead
`phone`	No	Phone number of the lead
`title`	No	Job title of the lead
`company`	No	Company of the lead
`last_name`	No	Last name of the lead
`first_name`	No	First name of the lead
`campaign_id`	Yes	ID of the campaign to add the lead to
`custom_fields`	No	Custom fields for the lead

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 18, 2025

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description solely states 'Add a new lead' without disclosing side effects, idempotency, duplicate handling, or required permissions.

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 description is a single, clear sentence with no wasted words, though it could be slightly more informative without losing brevity.

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 8 parameters including a nested object, no output schema, and no annotations, the description lacks critical context about return values, error conditions, and parameter usage nuances.

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 description adds no extra meaning beyond the schema's parameter descriptions; baseline 3 applies.

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 'Add a new lead to a campaign' includes a specific verb and resource, clearly distinguishing it from sibling tools like delete or bulk import.

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?

No guidance on when to use this tool versus alternatives such as smartlead_bulk_import_leads, nor any prerequisites or exclusions.

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