Nextmail

Add contact to audience

addContactToAudience

Put a contact in an audience. By default the contact has to exist already, because a mistyped address would become a permanent row nobody asked for: the createContact tool adds it first, or pass createContact: true to save the address as a contact on the spot. Adding somebody to a list sends nothing to them.

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

Input Schema

Name	Required	Description
`email`	Yes
`audienceId`	Yes
`createContact`	No	When true, an address that is not a contact yet is saved as one first, which also needs the contacts:write scope. Left out or false, such an address is refused.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / createContact

Added value: +{
+  "description": "When true, an address that is not a contact yet is saved as one first, which also needs the contacts:write scope. Left out or false, such an address is refused.",
+  "type": "boolean"
+}

First observedOct 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description adds real value on top by clarifying that the default refuses unknown addresses and that adding to a list 'sends nothing to them' – an important side-effect guarantee. It stops short of describing what happens when the contact is already a member (idempotency) or required scopes beyond the schema's contacts:write note.

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, front-loaded with the action, then the precondition and its rationale, then the alternative and the side-effect note. No filler sentences; each clause earns its place.

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?

For a three-parameter mutation with a clear annotation profile and no output schema, the description covers the essential decision points: prerequisite, alternative tool, flag behavior, and no-email side effect. Idempotency on duplicate membership and the return shape remain unaddressed.

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 only 33% – email and audienceId are undocumented in both places, though their names are self-evident. The description reinforces the createContact flag's default/refusal behavior, but this largely restates the schema's own description rather than adding new detail.

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?

States a concrete verb+resource ('Put a contact in an audience') that an agent can act on immediately. It does not distinguish itself from the plural sibling addContactsToAudience, so batch-vs-single routing is left to inference.

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

Usage Guidelines5/5

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

Explicitly states the default precondition (the contact must already exist), names the alternative (createContact first), and gives the in-call escape hatch (createContact: true). The reasoning for the constraint is supplied, so the agent can decide without probing.

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

All Nextmail tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.