Skip to main content
Glama

send16-mcp

by io.github.spruikco
OverviewDiscussionsAdmin

create_contact

Add a single new contact, optionally straight into audiences and/or with tags — e.g. 'add this person from my email into the newsletter list'. Contacts are subscribed by default. For more than a handful of people, use import_contacts instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTag NAMES to assign — matched case-insensitively, created if missing
emailYesContact email address
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)
lastNameNoContact last name
firstNameNoContact first name
audienceIdsNoAdd the contact to these audience IDs (see list_audiences)
customFieldsNoCustom field key-value pairs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / audienceIds
      Added value: +{
+  "description": "Add the contact to these audience IDs (see list_audiences)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / tags / description
      Previous value: -"Tag names to assign to this contact"New value: +"Tag NAMES to assign — matched case-insensitively, created if missing"
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds one significant behavior: 'Contacts are subscribed by default.' However, it does not disclose outcomes for duplicate emails, error handling, or response format. For a create operation, the default subscription note is useful but the description leaves ambiguity around idempotency and failure modes.

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?

The description is two sentences, front-loaded with the core purpose ('Add a single new contact'), followed by an illustrative example, a key behavioral default, and an explicit alternative. Every sentence earns its place with no filler or redundancy.

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 create tool with 7 parameters and no output schema, the description covers the essential context: the singular nature, optional audience/tag integration, default subscription, and bulk alternative. It does not describe return values or duplicate-handling, but the output schema is absent and the tool is relatively straightforward. The completeness is slightly limited by not addressing what happens if the email already exists, but overall it provides sufficient context for an AI agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so a baseline of 3 is appropriate. The description adds meaningful context by highlighting the optional combination of 'audiences and/or with tags', which maps to audienceIds and tags params. The example also clarifies how these parameters are used in a realistic scenario, providing value beyond the individual schema descriptions.

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 single new contact', specifying the resource (contact) and the operation (create). It also distinguishes from sibling tools by explicitly contrasting with import_contacts, and the example 'add this person from my email into the newsletter list' clarifies the intended use case.

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?

The description provides explicit usage guidance: it states the tool is for adding a single contact, optionally with audiences/tags, and gives a clear alternative for bulk operations: 'For more than a handful of people, use import_contacts instead.' This directly addresses when to use this tool versus a sibling.

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

All send16-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources