Skip to main content
Glama
jonathan-politzki

Smartlead Simplified MCP Server

smartlead_create_manual_placement_test

Create a manual placement test to evaluate email deliverability across different providers using Smartlead mailboxes, checking spam filters and link domains.

Instructions

Create a manual placement test using Smartlead mailboxes to test email deliverability across various email providers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
all_email_sent_without_time_gapYesSet true to send all emails simultaneously
campaign_idYesCampaign ID for which you want to select the sequence to test
descriptionNoDescription for your test to reference later
is_warmupYesSet true to receive positive intent responses and move emails from spam to inbox
link_checkerYesEnable to check if domains for links in email body are blacklisted
min_time_btwn_emailsYesTime gap between each email from each mailbox (if time gap enabled)
min_time_unitYesTime unit for the time gap (minutes, hours, days)
provider_idsYesArray of provider IDs to send test emails to
sender_accountsYesArray of email addresses to use as senders
sequence_mapping_idYesThe ID of the sequence or variant you would like to test
spam_filtersYesArray of spam filters to test across, e.g. ["spam_assassin"]
test_nameYesName of your test
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a test but doesn't cover critical aspects like whether this is a mutating operation, what permissions are required, if it triggers email sends immediately, rate limits, or what the output looks like. This is a significant gap for a tool with 12 parameters and no output schema.

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, efficient sentence that front-loads the core purpose without unnecessary details. Every word earns its place, making it easy to parse quickly.

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 the complexity (12 parameters, 11 required, no annotations, no output schema), the description is insufficient. It doesn't explain the tool's behavior, output, or integration with other tools (like the automated test sibling), leaving the agent with critical gaps despite the detailed schema.

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 fully documents all 12 parameters. The description adds no additional parameter semantics beyond what's in the schema, such as explaining relationships between parameters (e.g., how 'all_email_sent_without_time_gap' interacts with time gap parameters). Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the verb ('create') and resource ('manual placement test') with the specific goal of testing email deliverability across providers using Smartlead mailboxes. It distinguishes from the sibling 'smartlead_create_automated_placement_test' by specifying 'manual,' but doesn't explain the functional difference between manual and automated tests.

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 explicit guidance on when to use this tool versus alternatives like the automated placement test sibling. The description mentions the purpose but lacks context on prerequisites, typical use cases, or exclusions, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jonathan-politzki/smartlead-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server