Smartlead Simplified MCP Server

smartlead_list_campaigns

List your Smartlead campaigns with optional filtering by status, limit, and offset for pagination.

Instructions

List all campaigns with optional filtering.

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_campaigns"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of campaigns to return
`offset`	No	Offset for pagination
`status`	No	Filter campaigns by status

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?

No annotations provided; description only says 'list', implying read-only, but does not disclose pagination behavior, default limits, ordering, or any side effects. Minimal behavioral context.

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

Conciseness5/5

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

Single sentence, front-loaded with action and resource, no unnecessary words. Perfectly concise.

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?

No output schema, so description must explain return values and pagination. It does not. For a list tool with optional filters, information on default behavior, max results, and response format is missing.

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% with descriptions for all parameters. Description adds no extra meaning beyond schema, which is acceptable at baseline 3.

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?

Description clearly states verb 'List' and resource 'campaigns', with optional filtering. Implicitly distinguishes from siblings like smartlead_get_campaign (single) and smartlead_get_campaigns_by_lead (filtered by lead), but lacks explicit differentiation.

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 vs alternatives. Does not mention that for a single campaign, use smartlead_get_campaign, or for campaigns by lead, use smartlead_get_campaigns_by_lead.

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