shiply

Configure a site collection's email behavior

set_mailbox

Idempotent

Turn a Site Data collection into a mailbox: double opt-in, owner notifications, sending domain, branding. Call once per (site, collection) to configure how captured leads are handled.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	site slug the collection belongs to
`branding`	No	branding applied to mailbox emails
`notifyTo`	No	address to send owner notifications to
`collection`	Yes	Site Data collection to turn into a mailbox
`doubleOptIn`	No	require email confirmation before a contact is active
`notifyOwner`	No	email the owner on each new capture
`sendingDomainId`	No	BYO sending domain id to send from

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedJun 23, 2026

addedInput schema / properties / branding / description
```
Added value: +"branding applied to mailbox emails"
```
addedInput schema / properties / branding / properties / brandColor / description
```
Added value: +"accent color hex, e.g. #2563eb"
```
addedInput schema / properties / branding / properties / brandName / description
```
Added value: +"brand name shown in emails"
```
addedInput schema / properties / branding / properties / logoUrl / description
```
Added value: +"logo image URL shown in emails"
```

addedInput schema / properties / collection / description

Added value: +"Site Data collection to turn into a mailbox"

addedInput schema / properties / doubleOptIn / description

Added value: +"require email confirmation before a contact is active"

addedInput schema / properties / notifyOwner / description
```
Added value: +"email the owner on each new capture"
```

addedInput schema / properties / notifyTo / description

Added value: +"address to send owner notifications to"

addedInput schema / properties / sendingDomainId / description
```
Added value: +"BYO sending domain id to send from"
```

addedInput schema / properties / slug / description

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

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.6/5.0

Behavior3/5

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

The description mentions key behaviors (double opt-in, owner notifications, sending domain, branding) and the 'call once' guideline aligns with the idempotentHint annotation. It does not contradict annotations but adds limited depth beyond what annotations already provide.

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 two sentences with no wasted words. It front-loads capabilities and usage instruction efficiently. Every sentence earns its place.

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?

Given the tool's complexity (7 params, nested object, output schema), the description provides necessary context about what it does and when to call it. It is complete enough, though it could mention effects on existing configurations.

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% with each parameter described. The description lists features that map to parameters but does not add new semantics or constraints beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool turns a Site Data collection into a mailbox and lists key capabilities (double opt-in, notifications, etc.). It is specific about the resource and action, but does not explicitly differentiate from sibling tools like send_mailbox_broadcast or list_mailbox_contacts.

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 advises calling once per (site, collection), giving a usage hint. However, it does not specify when not to use this tool or mention alternatives. The context is implied but not explicit.

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?