send16-mcp

create_contact

Add a new contact to your Send16 audience. Contacts are automatically subscribed to receive emails.

Instructions

Add a new contact to your Send16 audience. Contacts are automatically subscribed to receive emails.

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

Input Schema

Name	Required	Description
`tags`	No	Tag names to assign to this contact
`email`	Yes	Contact email address
`apiKey`	No	Send16 API key (overrides SEND16_API_KEY env var)
`lastName`	No	Contact last name
`firstName`	No	Contact first name
`customFields`	No	Custom field key-value pairs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.7Jul 11, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions auto-subscription but omits critical details: handling of duplicate emails, confirmation emails, rate limits, or success/failure behavior. The agent lacks sufficient behavioral context to use this tool safely.

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?

Two sentences, no redundant information, front-loaded with the core action. Every word earns its place.

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

Completeness2/5

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

For a mutation tool with 6 parameters (including nested objects) and no output schema or annotations, the description is too sparse. It fails to explain return value, error cases, or duplicate contact behavior, leaving the agent under-informed.

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%, so baseline is 3. The description adds no parameter-specific information beyond what the schema already provides, but does not detract.

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?

The description clearly states the action (Add a new contact) and the resource (Send16 audience), and distinguishes from siblings like update_contact and delete_contact by specifying 'Add a new contact' and noting auto-subscription.

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?

The description implicitly suggests use for adding new contacts, but provides no explicit guidance on when to use this tool versus alternatives like import_contacts or add_contacts_to_audience, nor any when-not-to-use conditions.

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

Deploy Server