Meisa

Create Sequence

meisa_create_sequence

Create a new email automation sequence in Meisa in draft status. A sequence is a multi-step drip campaign that contacts are enrolled in over time. This creates the sequence container in draft. Add the drip steps with meisa_add_sequence_step (email -> delay -> email ...), then activate it with meisa_activate_sequence. Returns the created sequence with its auto-generated slug.

Input Schema

Name	Required	Description	Default
`name`	Yes	Name of the sequence (e.g. 'New User Onboarding', 'Trial Conversion').
`sender_id`	No	UUID of the sender identity for all emails in this sequence. Uses product default if omitted.
`description`	No	Internal description of what this sequence does.
`track_opens`	No	Add the open-tracking pixel. Default true. Set false to skip it (open stats are not recorded).
`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).
`entry_trigger`	No	How contacts enter this sequence. 'api' means enrollment via the meisa_enroll_in_sequence tool. 'tag_added' means automatically when a tag is added. Defaults to 'api'.	api
`email_category`	No	Subscription category, so recipients can unsubscribe from this kind of email and keep the rest: 'onboarding' (tips and onboarding), 'product_updates', 'promotions' (offers and discounts), 'newsletter'. Empty string = automatic: the template's category decides (promotional -> promotions, announcement -> product_updates, newsletter -> newsletter), otherwise sequences and triggers use 'onboarding' and broadcasts use 'product_updates'. Ignored on triggers with override_unsubscribe (those are transactional and always send).

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"
+}

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare it is not read-only but also not destructive/idempotent, which is a low bar to clear. The description adds genuinely useful state information beyond that: the sequence is created in draft status and is inert until meisa_activate_sequence is called, and it returns the created sequence with an auto-generated slug. It does not mention permission requirements or whether name uniqueness is enforced.

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, front-loaded with the action and result state, then the definition, then the follow-up workflow. No filler and nothing repeated from the schema.

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?

Even without an output schema, the description states what is returned (the created sequence with its auto-generated slug), and it covers the lifecycle position (draft) plus the steps needed to make it functional. An agent has everything needed to call it correctly and knows what to do next.

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 all seven parameters including the enums for entry_trigger and email_category and the defaults for tracking flags. The description adds no parameter-level detail (e.g., how entry_trigger interacts with meisa_enroll_in_sequence beyond what the schema says), so the baseline 3 is appropriate.

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 automation sequence') and immediately distinguishes the artifact from siblings by defining it as a multi-step drip campaign container, versus broadcasts/templates/triggers. An agent can tell this apart from meisa_create_broadcast or meisa_create_trigger without opening either 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 explicit workflow context: it creates the container in draft, steps are added via meisa_add_sequence_step, and it is activated via meisa_activate_sequence. That is strong forward routing, but there is no explicit when-not guidance (e.g., one-off sends should use meisa_send_broadcast, or existing sequences should use meisa_update_sequence).

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?