Emailchaser

Copilot: launch a draft campaign

copilot_launch

Creates a DRAFT campaign from a sequence. With a LinkedIn Sales Navigator search it also starts finding + verifying leads for it; without one the draft holds the emails and leads can be added from Lead Finder or a CSV upload. Nothing sends — the campaign stays a draft until you review and launch it. Returns the new campaign id, plus a lead-finding job id when lead finding started.

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

Input Schema

Name	Required	Description
`icp`	No	Optional ICP object as returned by copilot_plan, stored with the campaign for reference only
`name`	Yes	Campaign name
`sequence`	Yes	The email sequence: the first step is the initial email, the rest are follow-ups
`salesNavData`	No	Optional base64 LinkedIn session payload from the browser extension; required for lead-finding to actually run
`salesNavSearchUrl`	No	Optional LinkedIn Sales Navigator people-search URL to source leads from. Leave it out to create the draft with its emails only. Required when salesNavData is given.

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"

Changed3 schema fields changedOct 1, 2026

changedInput schema / properties / salesNavSearchUrl / description

Previous value: -"A LinkedIn Sales Navigator people-search URL to source leads from"New value: +"Optional LinkedIn Sales Navigator people-search URL to source leads from. Leave it out to create the draft with its emails only. Required when salesNavData is given."

removedInput schema / properties / salesNavSearchUrl / minLength
```
Removed value: -1
```

changedInput schema / required

Previous value: -[
-  "name",
-  "salesNavSearchUrl",
-  "sequence"
-]New value: +[
+  "name",
+  "sequence"
+]

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 non-read-only, open-world, non-idempotent, non-destructive; the description adds the crucial safety guarantee that no email is sent and that the object remains a draft, plus the side effect of starting a lead-finding/verification job. It does not warn about duplicate campaigns on repeat calls or what verification consumes.

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?

Four compact sentences, front-loaded with purpose, then branching behavior, then the no-send guarantee, then the return values. No filler; each clause carries distinct information.

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?

With no output schema, the description usefully names what is returned (campaign id plus optional lead-finding job id). For an open-world mutation that spawns a background job, it could still say whether verification is async or what happens when salesNavData is supplied without a URL.

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% and the schema already explains salesNavData/salesNavSearchUrl coupling and sequence structure, so the description only restates that pairing at a higher level. It adds no syntax, format, or constraint detail beyond what the input schema provides.

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 and resource ('Creates a DRAFT campaign from a sequence') plus the conditional branching behavior, and the emphasis on DRAFT plus 'nothing sends' distinguishes it from the launch/create siblings without naming them.

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 conditional guidance: supply a Sales Navigator search to also kick off lead finding, omit it to hold only the emails and add leads later via Lead Finder or CSV. It implies the review-then-launch path ('until you review and launch it') but does not explicitly name launch_campaign or create_campaign as alternatives.

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?