[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)

# Email candidates from a job

> Send one email to several candidates of a job, each as an individual message. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/loxo/send_email

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)

Send one email to several candidates of a job, each as an individual message.

Loxo MCP tools: https://cotlet.dev/docs/mcp/loxo.md

MCP tool: `loxo_write → send_email`

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

Sends from the job pipeline, as the Email button does, so each email is linked to the job. Loxo sends every recipient an individual message, so they do not see each other. A person with no address of that type is skipped and listed in the response. It sends text only: no merge tags, attachments or SMS. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job id, so Loxo links the email to the job. |
| `person_ids` | array | yes | Person ids of the recipients. |
| `subject` | string | yes | Subject line. |
| `body` | string | yes | Plain-text message, sent as written to every recipient. |
| `email_type` | string | no | Email type to send to, for example Personal or Work. Default: the primary email, the first listed on the record. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "loxo_write",
    "arguments": {
      "operation": "send_email",
      "arguments": {
        "job_id": 2481530,
        "person_ids": [
          48211077,
          48211102,
          48211130
        ],
        "subject": "Senior Data Engineer: client call moved to Thursday",
        "body": "Hi, the client call has moved to Thursday at 3 pm. Please reply to confirm you can make it."
      }
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "job_id": 2481530,
    "sent": 3,
    "email_type": "Primary",
    "recipients": [
      {
        "person_id": 48211077,
        "name": "Priya Nair",
        "status": "sent"
      },
      {
        "person_id": 48211102,
        "name": "Tom Becker",
        "status": "sent"
      },
      {
        "person_id": 48211130,
        "name": "Lena Ortiz",
        "status": "sent"
      }
    ],
    "skipped": []
  },
  "isError": false
}
```

Previous: [Add people to a list](https://cotlet.dev/docs/mcp/loxo/add_to_list.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.