[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Add recipients

> Add people to a campaign with a name and custom fields for the text replacements in your emails. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/mailshake/add_recipients

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Add people to a campaign with a name and custom fields for the text replacements in your emails.

Mailshake MCP tools: https://cotlet.dev/docs/mcp/mailshake.md

MCP tool: `mailshake_write → add_recipients`

Access: write. Confirm: waits for the user's OK before it runs.

Adds recipients to a campaign and waits for Mailshake to finish the import, then returns what was skipped. Addresses on your unsubscribe list and addresses already in the campaign are skipped. A campaign holds up to 5,000 recipients through the API, and your plan limits how many recipients you can add per month. Unless the campaign is paused, new recipients are scheduled to get its emails right away. A field your emails use as a text replacement but a recipient lacks keeps that recipient's emails from being scheduled. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | integer | yes | Campaign ID from list_campaigns. |
| `addresses` | object[] | yes | Each item: email_address (required), full_name, and fields, an object of custom values such as company. Mailshake adds first, last and name text replacements from full_name. Up to 30 fields per recipient. |
| `add_as_new_list` | boolean | no | true to keep these recipients grouped as their own list. Default: false, they join the last list you uploaded. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "mailshake_write",
    "arguments": {
      "operation": "add_recipients",
      "arguments": {
        "campaign_id": 4821,
        "addresses": [
          {
            "email_address": "dana@brightpath.example",
            "full_name": "Dana Whitfield",
            "fields": {
              "company": "Brightpath"
            }
          },
          {
            "email_address": "omar@lumenlabs.example",
            "full_name": "Omar Haddad",
            "fields": {
              "company": "Lumen Labs"
            }
          },
          {
            "email_address": "li@oldclient.example",
            "full_name": "Li Chen",
            "fields": {
              "company": "Old Client"
            }
          }
        ],
        "add_as_new_list": true
      }
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "campaign_id": 4821,
    "submitted": 3,
    "added": 2,
    "invalid_emails": [],
    "problems": {
      "unsubscribed_emails": [
        "li@oldclient.example"
      ],
      "already_in_campaign_emails": [],
      "over_campaign_limit_emails": []
    }
  },
  "isError": false
}
```

Previous: [List leads](https://cotlet.dev/docs/mcp/mailshake/list_leads.md)
Next: [Pause campaign](https://cotlet.dev/docs/mcp/mailshake/pause_campaign.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.