Smartlead Simplified MCP Server

smartlead_get_campaign_sequence_analytics

Retrieve analytics data for a specific email campaign sequence by providing campaign ID and date range.

Instructions

Fetch analytics data for a specific email campaign sequence.

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>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "smartlead_get_campaign_sequence_analytics"
  }
}

Input Schema

Name	Required	Description
`end_date`	Yes	End date in YYYY-MM-DD HH:MM:SS format
`time_zone`	No	Timezone for the analytics data (e.g., "Europe/London")
`start_date`	Yes	Start date in YYYY-MM-DD HH:MM:SS format
`campaign_id`	Yes	ID of the campaign to fetch sequence analytics for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 18, 2025

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, and the description only states 'Fetch analytics data' without disclosing any behavioral traits such as data freshness, permissions required, rate limits, or format of returned data.

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?

The description is one concise sentence that directly states the purpose without any extraneous words. Every word earns its place.

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 4 parameters (3 required) and no output schema or annotations, the description is too brief. It does not explain what analytics metrics are returned, data range constraints, or pagination, 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 description coverage is 100%, so the schema itself documents all parameters. The description does not add any additional meaning beyond the schema baseline, resulting in a score of 3.

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 the action ('Fetch analytics data') and the specific resource ('specific email campaign sequence'), distinguishing it from sibling tools like smartlead_get_campaign_analytics_by_date which fetches campaign-level analytics not sequence-level.

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., smartlead_get_campaign_analytics_by_date), no prerequisites or exclusions provided.

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