Meisa

Update Broadcast

meisa_update_broadcast

Idempotent

Edit a DRAFT broadcast's fields (PATCH-style; only the fields you pass change). Once a broadcast is scheduled, sending, or sent it is locked and this returns a 409. Use this to fix the name, subject override, audience segment, template, or sender before sending. Pass thread_broadcast_id to send it as a reply in the inbox thread of an earlier sent broadcast.

Input Schema

Name	Required	Description
`name`	No	New internal name.
`sender_id`	No	New sender identity UUID, or empty string to clear to the product default.
`description`	No	New internal description.
`template_id`	No	Repoint to a different template (must exist in this product).
`track_opens`	No	Add the open-tracking pixel. Default true. Set false to skip it (open stats are not recorded).
`broadcast_id`	Yes	UUID of the draft broadcast to edit.
`track_clicks`	No	Wrap links in click-tracking redirects. Default true. Set false to send links straight to the destination (can help inbox placement; click stats are not recorded).
`segment_query`	No	Replace the audience segment rules, e.g. {"rules": [{"field": "tag", "operator": "has", "value": "pro"}]}.
`email_category`	No	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 subject. Empty string clears it.
`subject_override_b`	No	Second subject for a 50/50 A/B test. Requires subject_override.
`thread_broadcast_id`	No	UUID of an earlier, already sent broadcast of this product to reply in the thread of. Recipients of that broadcast get this one as a reply in the same inbox thread, with the subject "Re: <earlier subject>" when subject_override is empty. Pass null to send as a normal new email again.
`preview_text_override`	No	Override the template preview text.
`preview_text_override_b`	No	Second preview text for the A/B variant B.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 12, 2026

addedInput schema / properties / track_clicks

Added value: +{
+  "description": "Wrap links in click-tracking redirects. Default true. Set false to send links straight to the destination (can help inbox placement; click stats are not recorded).",
+  "type": "boolean"
+}

addedInput schema / properties / track_opens

Added value: +{
+  "description": "Add the open-tracking pixel. Default true. Set false to skip it (open stats are not recorded).",
+  "type": "boolean"
+}

Changed1 schema field changedOct 10, 2026

addedInput schema / properties / thread_broadcast_id

Added value: +{
+  "anyOf": [
+    {
+      "format": "uuid",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "UUID of an earlier, already sent broadcast of this product to reply in the thread of. Recipients of that broadcast get this one as a reply in the same inbox thread, with the subject \"Re: <earlier subject>\" when subject_override is empty. Pass null to send as a normal new email again."
+}

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 already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, but the description adds genuinely new behavior: PATCH-style partial updates (only passed fields change), the immutable-state rule (scheduled/sending/sent), and the concrete 409 failure mode. This is exactly the extra context annotations cannot express.

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?

Three sentences, zero filler. The most decision-relevant fact (draft-only, partial update) is front-loaded, the lock/409 caveat follows, and the thread_broadcast_id note is placed last as a secondary behavior.

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

Completeness5/5

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

For a 14-parameter mutation tool with no output schema, the description covers the safety profile, mutation semantics, failure condition, and the non-obvious threading behavior. An agent has everything needed to call it correctly and interpret the main error case.

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 every parameter is already documented in detail in the schema, which sets the baseline at 3. The description restates a subset of editable fields (name, subject override, segment, template, sender) without adding format or syntax beyond the schema, though it does frame thread_broadcast_id as the reply-threading switch.

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 and resource ('Edit a DRAFT broadcast's fields') and immediately scopes it with PATCH-style semantics. The draft-only constraint distinguishes it from meisa_schedule_broadcast, meisa_send_broadcast, and meisa_cancel_broadcast without needing to open any schema.

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?

Gives a clear when-to-use ('Use this to fix the name, subject override, audience segment, template, or sender before sending') and an explicit when-not ('Once a broadcast is scheduled, sending, or sent it is locked and this returns a 409'). It does not name sibling alternatives such as meisa_update_template or meisa_duplicate_broadcast, which keeps it just short of a 5.

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?