Skip to main content
Glama
spruikco

send16-mcp

by spruikco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_messages

Retrieve and filter messages from the unified send log by recipient, sender, status, date range, or source.

Instructions

List messages from the unified send log (transactional + campaign). Filter by recipient, sender, status, date range, or source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size (default 50)
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)
offsetNoPage offset
sourceNoRestrict to one message source
statusNoDelivery status filter
to_emailNoRecipient email filter
from_emailNoSender email filter
created_afterNoISO-8601 timestamp lower bound
created_beforeNoISO-8601 timestamp upper bound

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.7

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose important behavioral traits such as pagination behavior, ordering, rate limits, data freshness, or permission requirements. The description only states basic functionality.

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 action and resource, followed by filter summary. No wasted words, efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is incomplete given the complexity: 9 parameters, no output schema, no annotations. It fails to explain pagination (limit/offset), default ordering, potential large result sets, or the shape of the returned data. More context is needed for an agent to use the tool effectively.

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%, so baseline is 3. The description adds a summary of filter categories (recipient, sender, status, date range, source) but does not provide new meaning beyond the schema. No note about default values or usage hints.

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 specifies a clear verb ('List'), a specific resource ('messages from the unified send log'), and explicitly mentions filtering capabilities. It distinguishes from sibling tools like 'get_message' and other list tools by highlighting the unified log and filter options.

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 implies usage for retrieving messages with filters but does not explicitly state when to use this tool versus alternatives like 'get_message' for single messages or other list tools. However, the naming and context are clear enough.

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