send16-mcp

create_topic

Create a subscription topic for contacts to opt into individually through the preference center.

Instructions

Create a new subscription topic. Contacts opt into topics individually via the preference center.

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

Input Schema

Name	Required	Description
`name`	Yes	Display name shown to contacts
`slug`	No	URL-safe slug (auto-derived from name if omitted)
`apiKey`	No	Send16 API key (overrides SEND16_API_KEY env var)
`isDefault`	No	Auto-subscribe new contacts to this topic
`description`	No	Description shown in the preference center

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.7Jul 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations, but description adds behavioral context: topics are opt-in via preference center. Beyond what schema provides.

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?

Single sentence with all necessary high-level information, front-loaded and efficient.

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?

As a creation tool, description could mention return value (e.g., created topic object or ID). Otherwise adequate given parameter richness.

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 100% with descriptions for all 5 parameters. Description adds no extra parameter-level meaning, so baseline 3 is appropriate.

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?

Clearly states it creates a new subscription topic and adds context about opt-in via preference center. Distinguishes from siblings like delete_topic, update_topic, and list_topics.

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?

Implies use when creating a new topic, but no explicit when-not-to-use or alternatives. Sibling names suggest typical CRUD pattern.

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

Deploy Server