Emailchaser

Create campaign

create_campaign

Creates a campaign in the workspace. The campaign starts as a DRAFT and sends nothing. A new campaign has no emails in it, so it cannot be launched until a sequence is written with replace_campaign_sequence and a sender email is attached. Sending limits and deliverability settings can be set here or changed later with update_campaign.

Input Schema

TableJSON Schema

Name	Required	Description
`flow`	No	Campaign flow. Defaults to multiple_leads_scheduled, which behaves exactly like a campaign created in the app. Only pass api if you specifically want lead validation skipped at launch
`name`	Yes	Campaign name
`emoji`	No	Campaign emoji shown in the app. Defaults to a generic one
`timezone`	No	IANA timezone, e.g. America/New_York
`dailyLimit`	No	Cap on the total emails (initial + follow-ups) the campaign may schedule per calendar day in its timezone. Omit for no campaign-level cap; per-mailbox limits still apply
`isEnabledLlm`	No	Enable AI (LLM) features for this campaign
`minimumHealthScore`	No	Minimum email account health score for this campaign, 1-100 (see healthScore in list_sender_emails). An account below it, or with no score yet, sends nothing in this campaign, first emails and follow-ups alike, until its score is back at or above it; its conversations wait for it and never move to another account. 0 means no minimum; omit it to leave the setting as it is
`allowNonBusinessEmails`	No	Allow sending to free mailbox providers (gmail.com, etc.)
`isEnabledEmailVerifier`	No	Verify lead emails before sending
`ignoreOutOfOfficeReplies`	No	Do not stop follow-ups on out-of-office replies
`maximumTimeBetweenEmails`	No	Maximum gap between two sends, in minutes
`minimumTimeBetweenEmails`	No	Minimum gap between two sends, in minutes
`isEnabledCatchallValidated`	No	Send to catch-all validated addresses
`isEnabledStopFollowUpsOnReply`	No	Stop follow-ups to a lead once they reply
`isEnabledIgnoreHardBouncedLeads`	No	Skip leads that previously hard-bounced
`isEnabledSkipLeadIfAlreadyExists`	No	Skip leads that already exist in the workspace
`maximumSendingLimitPerSenderEmail`	No	Daily sending limit per sender email account
`isEnabledStopFollowUpsForSameCompany`	No	Company reply stop: once a lead replies (out-of-office and other automatic replies don't count), stop emailing the other leads at the same company in this campaign. Subdomains count as the same company; personal addresses like @gmail.com never do. On by default
`isEnabledIgnoreLeadsWhoAlreadyResponded`	No	Skip leads who already responded in another campaign
`maximumSendingLimitPerSenderEmailVariation`	No	Random daily variation applied to the sending limit

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / minimumHealthScore

Added value: +{
+  "description": "Minimum email account health score for this campaign, 1-100 (see healthScore in list_sender_emails). An account below it, or with no score yet, sends nothing in this campaign, first emails and follow-ups alike, until its score is back at or above it; its conversations wait for it and never move to another account. 0 means no minimum; omit it to leave the setting as it is",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / isEnabledStopFollowUpsForSameCompany / description

Previous value: -"Stop follow-ups to a company once someone there replies"New value: +"Company reply stop: once a lead replies (out-of-office and other automatic replies don't count), stop emailing the other leads at the same company in this campaign. Subdomains count as the same company; personal addresses like @gmail.com never do. On by default"

First observedSep 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare openWorldHint=false and destructiveHint=false; the description adds real behavioral context beyond them — the new campaign is a non-sending DRAFT with no emails, and launch is blocked until sequence and sender are added. It does not describe return values, but the state/lifecycle disclosure is meaningful added value.

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?

Three tight sentences, front-loaded with the core action, then the resulting state, then the prerequisite chain, then where settings live. Every sentence earns its place with no redundancy.

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

Completeness4/5

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

For a 20-parameter creation tool with full schema coverage and no output schema, the description supplies the key lifecycle and prerequisite information an agent needs to sequence these calls correctly. It does not mention what the call returns, but with no output schema that is a minor gap against otherwise strong coverage.

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 already documents all 20 parameters in detail. The description only groups them loosely ('sending limits and deliverability settings can be set here'), adding no per-parameter 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?

States a specific verb+resource ('Creates a campaign in the workspace') and distinguishes it from siblings by naming replace_campaign_sequence and update_campaign in context. The DRAFT lifecycle statement further clarifies what this tool specifically does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear prerequisites and lifecycle context: the campaign starts as a DRAFT, sends nothing, and cannot be launched until a sequence is written and a sender email attached. It names the follow-up tools (replace_campaign_sequence, update_campaign) but does not phrase explicit when-to-use/when-not conditions, so it falls just short of a 5.

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

All Emailchaser tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?