Skip to main content
Glama
Sign In
send16-mcp

send16-mcp

by spruikco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

preview_segment

View the list of contacts that match a specific segment to verify targeting before sending.

Instructions

Preview the contacts that match a segment without sending.

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

Input Schema

NameRequiredDescriptionDefault
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)
segmentIdYesSegment ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.7

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It clearly indicates no sending occurs, implying read-only behavior. However, it omits details like rate limits, required permissions, or whether the preview is real-time or cached.

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, no extraneous words. Front-loaded with the action. Efficient and to the point.

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?

Simple tool with few parameters; the description covers the core function. However, the output format is not described (e.g., list of contacts, count). Completeness is high for the tool's complexity but could be slightly improved.

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%. The description does not add new meaning beyond the schema; it reiterates that segmentId identifies the segment. Baseline 3 is appropriate as the schema already documents both parameters adequately.

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 'Preview the contacts that match a segment without sending' clearly states the verb (preview), resource (contacts matching a segment), and subtly distinguishes from sending operations. It is specific and avoids ambiguity.

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 implies usage for dry-run preview but does not explicitly state when to use this tool versus alternatives like search_contacts or preview_campaign_recipients. No when-not or alternative recommendations are provided.

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

Deploy Server

Other Tools