shiply

Broadcast to a mailbox's confirmed audience

send_mailbox_broadcast

Send a one-shot broadcast to the confirmed (double-opt-in) subscribers of a (site, collection) mailbox. Spam-checked; unsubscribe footer auto-added. Fails if no confirmed subscribers exist yet.

Input Schema

TableJSON Schema

Name	Required	Description
`html`	Yes	email HTML body (unsubscribe footer added automatically)
`slug`	Yes	site slug the mailbox belongs to
`text`	No	plain-text fallback body
`subject`	Yes	email subject line
`collection`	Yes	mailbox collection whose confirmed audience to email

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedJun 23, 2026

addedInput schema / properties / collection / description

Added value: +"mailbox collection whose confirmed audience to email"

addedInput schema / properties / html / description

Added value: +"email HTML body (unsubscribe footer added automatically)"

addedInput schema / properties / slug / description

Added value: +"site slug the mailbox belongs to"

addedInput schema / properties / subject / description
```
Added value: +"email subject line"
```
addedInput schema / properties / text / description
```
Added value: +"plain-text fallback body"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedJun 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond annotations (openWorldHint, idempotentHint), the description reveals that the broadcast is 'one-shot', spam-checked, automatically adds an unsubscribe footer, and fails if no subscribers exist. This adds valuable behavioral context about safety and preconditions.

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 concise sentences: the first covers purpose and target, the second covers key constraints and traits. No unnecessary words, and critical information is front-loaded.

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?

The description covers core functionality, failure condition, and important traits (spam check, auto footer). With a full input schema and an output schema present, the description is sufficiently complete for the tool's complexity.

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 reiterates the role of 'slug' and 'collection' as defining the mailbox but adds no new parameter meaning beyond what the schema provides.

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 verb 'Send' and the specific resource: 'broadcast to the confirmed (double-opt-in) subscribers of a (site, collection) mailbox.' It distinguishes itself from generic broadcast tools by specifying the audience type and constraints.

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

Usage Guidelines2/5

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

The description mentions that it fails if no confirmed subscribers exist, but does not provide guidance on when to use this tool versus alternatives like 'send_broadcast' or 'send_email'. No explicit context for choosing this tool is given.

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

All shiply tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?