Skip to main content
Glama

send16-mcp

by io.github.spruikco
OverviewDiscussionsAdmin

import_contacts

Bulk import contacts from CSV data (min column: email), optionally straight into audiences and/or with tags. This is the tool for cross-app flows — e.g. pulling people out of Gmail, a CRM, or a spreadsheet and landing them in a Send16 audience in one call. Set updateExisting for upsert semantics (safe to re-run).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTag NAMES to apply to all imported contacts — matched case-insensitively, created if missing
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)
csvDataYesCSV string with headers. Required column: "email". Optional: "firstName", "lastName"
audienceIdsNoAdd all imported contacts to these audience IDs (see list_audiences / create_audience)
updateExistingNoWhether to update contacts that already exist

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / audienceIds
      Added value: +{
+  "description": "Add all imported contacts to these audience IDs (see list_audiences / create_audience)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / csvData / description
      Previous value: -"CSV string with headers. Required column: \"email\". Optional: \"firstName\", \"lastName\", \"tags\" (comma-separated within quotes)"New value: +"CSV string with headers. Required column: \"email\". Optional: \"firstName\", \"lastName\""
    • changedInput schema / properties / tags / description
      Previous value: -"Tag names to apply to all imported contacts"New value: +"Tag NAMES to apply to all imported contacts — matched case-insensitively, created if missing"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It reveals that imports are bulk, supports upsert semantics, and are safe to re-run with updateExisting. It also mentions optional audience/tag assignment. While error handling and permissions are not covered, the key behavioral traits are disclosed.

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 three sentences, front-loaded with the core purpose, followed by a use case and a practical tip. Every sentence contributes value and there is no 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 mutation tool with no annotations and no output schema, the description provides sufficient context: purpose, input requirements, optional parameters' roles, and re-run safety. It does not mention return values or failure modes, but the schema covers parameters and the description explains the main workflow.

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 descriptions already cover all 5 parameters (100% coverage), so the baseline is 3. The description adds value by clarifying that email is the minimum required column, explaining upsert semantics for updateExisting, and connecting audienceIds/tags to the one-call flow. This goes beyond the schema's basic 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 starts with a specific verb ('Bulk import contacts from CSV data') and names the required column. It differentiates this tool from siblings by calling it 'the tool for cross-app flows' and noting it can optionally place contacts into audiences/tags in one call, making its unique role clear.

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

Usage Guidelines4/5

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

The description offers clear when-to-use guidance ('This is the tool for cross-app flows') with concrete examples (Gmail, CRM, spreadsheet) and advises on the updateExisting parameter for safe re-runs. However, it does not explicitly state when not to use it or name alternative tools such as add_contacts_to_audience.

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