Smartlead Simplified MCP Server

smartlead_list_leads

Retrieve leads from Smartlead with optional filters for campaign, status, date range, or search term to organize and manage lead lists.

Instructions

List leads with optional filtering by campaign or status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "smartlead_list_leads"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of leads to return
`offset`	No	Offset for pagination
`search`	No	Search term to filter leads
`status`	No	Filter leads by status (e.g., "active", "unsubscribed", "bounced")
`end_date`	No	Filter leads created before this date (YYYY-MM-DD format)
`start_date`	No	Filter leads created after this date (YYYY-MM-DD format)
`campaign_id`	No	Filter leads by campaign ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 18, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description bears full disclosure burden. It does not mention pagination behavior (offset/limit), rate limits, or that it's a read-only operation. Only minimal filtering cues are given.

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?

One sentence, no fluff. It is succinct but could include more useful information without becoming lengthy.

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?

Lacks details about output format (e.g., array of lead objects) and default behavior. For a 7-param tool with no output schema, the description is too minimal to be fully complete.

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%, each parameter has a description. The description adds the phrase 'optional filtering by campaign or status' but adds no new semantic info beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'List leads' clearly indicating verb+resource. It mentions optional filtering by campaign or status, which aligns with the schema. However, it does not differentiate from siblings like smartlead_get_lead or smartlead_export_campaign_leads.

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 (e.g., export or single lead retrieval). The description lacks context for selection among 19 sibling tools.

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