Meisa

Create Broadcast

meisa_create_broadcast

Create a new email broadcast in Meisa in draft status. A broadcast sends one email to many contacts matching an audience segment. Requires a name and a template_id (use meisa_list_templates to find one). The broadcast is created as a draft and must be sent with meisa_send_broadcast. Do NOT use for one-to-one transactional emails. Use meisa_send_email for those. Optionally enable Warm Send (warm_send_enabled) to deliver in engagement-ranked chunks spaced over up to 24 hours. Top openers receive the email first, which protects sender reputation on large or low-engagement lists. Pass a non-empty subject_override_b to enable a 50/50 subject-line A/B test on this broadcast. Each recipient deterministically receives one variant (hashed by recipient + broadcast id) and analytics include per-variant open and click rates. subject_override_b requires subject_override to also be set.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Internal name for this broadcast (not shown to recipients).
`sender_id`	No	UUID of the sender identity to use. If omitted, the product default sender is used.
`description`	No	Internal description/notes about this broadcast.
`template_id`	Yes	UUID of the email template to use. Use meisa_list_templates to find available templates.
`segment_query`	No	Audience segment filter rules. Example: {"rules": [{"field": "status", "operator": "equals", "value": "active"}]}. If omitted, all active contacts are targeted.
`email_category`	Yes	REQUIRED. Which kind of email this broadcast is, so recipients can unsubscribe from just this kind: 'product_updates' (new features, improvements, important changes), 'promotions' (offers, discounts, sales, launches with a deal), 'newsletter' (regular articles and news), 'onboarding' (tips and onboarding). Unsubscribing from one category never stops the others. Pick 'product_updates' when unsure.
`subject_override`	No	Override the template's subject line for this broadcast.
`warm_send_enabled`	No	Enable Warm Send for this broadcast. When true, the audience is split into chunks ordered by historical open engagement (top openers first) and the chunks fire over up to 24 hours. Recommended for sends larger than ~5,000 contacts or for re-engagement campaigns to lists that have not been emailed recently. Default false.
`subject_override_b`	No	Optional second subject line. When set together with subject_override, the broadcast runs a 50/50 subject-line A/B test. Each recipient deterministically receives one of the two subjects. Requires subject_override to also be set.
`preview_text_override`	No	Override the template's preview text (the snippet most email clients show next to the subject in the inbox).
`preview_text_override_b`	No	Optional second preview text shown to recipients who receive subject variant B in an A/B test. Only used when subject_override_b is set.
`warm_send_chunk_gap_hours`	No	Hours between Warm Send chunks. Default 8. Total send window is always capped at 24 hours, so very large gaps are auto-compressed. Only used when warm_send_enabled is true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description goes well beyond that: the object is created in draft status and is inert until meisa_send_broadcast, and it explains the delivery semantics of Warm Send (engagement-ranked chunks over up to 24 hours) and the deterministic per-recipient variant assignment of the A/B test. These are non-obvious behavioral traits that materially affect how an agent invokes the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and lifecycle, then layered with the two optional feature explanations. It is longer than most definitions but nearly every sentence earns its place; only the draft-status statement is mildly redundant (said twice in the first and fourth sentences).

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?

For a 12-parameter, no-output-schema creation tool this is close to complete: creation state, dependencies, follow-up call, and both optional feature behaviors are covered. The one real gap is that it never says what is returned (e.g., the broadcast id needed to call meisa_send_broadcast), which matters because there is no output schema to fall back on.

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 the schema already documents every parameter thoroughly, making 3 the baseline. The description restates the warm_send_enabled and subject_override_b semantics and repeats the 'subject_override_b requires subject_override' constraint already present in the schema; it adds rationale (why warm send protects reputation) but little new syntactic meaning an agent couldn't get from the schema.

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?

States a specific verb+resource ('Create a new email broadcast in Meisa') plus the lifecycle state (draft) and the one-to-many nature of the resource. It explicitly distinguishes itself from meisa_send_email and points to meisa_send_broadcast for the send step, so an agent can separate it from its siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('a broadcast sends one email to many contacts matching an audience segment'), a naming alternative for the template dependency (meisa_list_templates), the follow-up tool (meisa_send_broadcast), and an explicit when-not ('Do NOT use for one-to-one transactional emails. Use meisa_send_email for those'). This is the full when/when-not/alternatives pattern.

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

All Meisa tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?