Skip to main content
Glama
Sign In
Smartlead Simplified MCP Server

Smartlead Simplified MCP Server

by jonathan-politzki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

smartlead_export_campaign_leads

Export all leads from a campaign as CSV to access and analyze your lead data.

Instructions

Export all leads data from a campaign as CSV.

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

Input Schema

NameRequiredDescriptionDefault
campaign_idYesID of the campaign to export leads from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states the output is CSV but does not explain how the CSV is delivered (e.g., download URL, streaming, or file path). No mention of authentication, rate limits, or side effects.

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 a single, short sentence that is front-loaded and contains no redundant words. It efficiently conveys the core purpose.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, no output schema), the description is adequate but lacks detail on the return format or behavior. It states 'as CSV' but does not specify how the output is provided, missing completeness for a standalone description.

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 a clear parameter description for campaign_id. The description adds the CSV format but does not provide additional semantic meaning beyond the schema. 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 clearly states the action (export), resource (all leads data from a campaign), and output format (CSV). It distinguishes from sibling tools like smartlead_list_leads or smartlead_get_lead, which are for listing or getting individual 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 is provided on when to use this tool versus alternatives, such as smartlead_list_leads for non-export needs. There are no preconditions, limitations, or context about appropriate scenarios.

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

Deploy Server

Other Tools