EmailOctopus MCP Server

Add or update contact

upsert_contact

Create or update a contact in an EmailOctopus list by email, set custom fields, add or remove tags, and assign subscription status.

Instructions

Create a contact, or update it if the email already exists in the list. Set custom fields by their tag (e.g. FirstName), add/remove tags, and set status.

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": {
      "listId": "<listId>",
      "email_address": "<email_address>"
    },
    "name": "upsert_contact"
  }
}

Input Schema

Name	Required	Description
`fields`	No	Custom field values keyed by field tag, e.g. {"FirstName": "Dana"}
`listId`	Yes	List ID (from list_lists)
`status`	No	Defaults to the list's opt-in setting for new contacts
`add_tags`	No
`remove_tags`	No
`email_address`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 18, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds useful behavior (custom fields keyed by tag, add/remove tags, status) but does not say whether an update overwrites or preserves omitted fields/tags, which matters for a non-destructive-flagged upsert.

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?

A single, front-loaded sentence that leads with the core create-or-update behavior. It is efficient with no wasted clauses, though it tries to pack three capabilities into one line.

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

Completeness3/5

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

For a 6-param mutation tool with no output schema, the description is adequate but thin: it omits the upsert-vs-update_contact routing decision and the overwrite semantics of updating an existing contact.

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 50%. The description explains that fields are set by tag, and mentions add/remove tags and status, adding meaning beyond the bare schema for those params. It does not address listId or email_address, though those are required and relatively self-evident.

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 states a specific verb and resource and clearly captures the upsert semantics ('Create a contact, or update it if the email already exists in the list'). However, it never distinguishes this from the sibling update_contact, so an agent can't tell from the description alone which one applies.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. With a sibling named update_contact that also mutates contacts, the choice between the two is left entirely to inference, which is a meaningful gap.

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

Deploy Server