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 it has a sequence and a sender email attached. Sending limits and deliverability settings can be set here or changed later.

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

Input 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 changedOct 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

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

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description goes beyond them by stating the campaign is created as a DRAFT, sends nothing, and is inert until a sequence and sender email exist — valuable safety context for a mutation tool. It stops short of covering idempotency (what happens on duplicate names) or whether an identifier is returned.

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

Conciseness4/5

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

Four short sentences, front-loaded with the action and its resulting state, with no filler. The closing sentence about sending limits and deliverability settings earns its place by discouraging over-configuration, though it is the softest of the four.

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, single-required-field mutation tool with no output schema, the description covers the essentials: what is created, its initial state, and the prerequisites before it becomes useful. The remaining gap is the return value — an agent cannot tell whether the new campaign's ID comes back for use in attach_campaign_sender_emails — but the rich schema compensates on the input side.

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% and the parameter descriptions are unusually rich (flow enum behavior, minimumHealthScore semantics, dailyLimit scope), so the schema does the heavy lifting. The description adds only a light frame — that sending limits and deliverability settings may be set now or later — which usefully signals these 19 optional params need not be supplied, but gives no per-parameter meaning.

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 opens with a specific verb and resource, 'Creates a campaign in the workspace,' and adds the resulting state (DRAFT, nothing sent), so an agent knows exactly what the call does. It does not name or contrast a sibling such as update_campaign, but 'creates' versus 'update' is unambiguous enough that differentiation is implicit rather than stated.

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

Usage Guidelines3/5

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

Usage context is implied rather than prescribed: the description explains that the campaign starts as a DRAFT and 'cannot be launched until it has a sequence and a sender email attached,' which effectively signals the follow-up calls an agent needs. It never states when to choose this tool over alternatives or what conditions make creation inappropriate, so an agent must infer the routing from the prerequisite sentence.

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?