Skip to main content
Glama
Sequenzy

Sequenzy MCP Server

Official

create_campaign

Draft an email campaign with AI-generated or custom content. Configure subject, tracking, segment, and labels for targeted marketing.

Instructions

Create a new campaign (as draft)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdNoCompany ID to create the campaign in. If not provided, uses the currently selected company.
nameYesCampaign name
subjectNoEmail subject line. Optional when `prompt` is provided because the generated subject will be used.
trackingCodeNoOptional campaign tracking code for UTM templates. Use only when explicitly requested.
htmlNoEmail HTML content. Mutually exclusive with `blocks`.
blocksNoSequenzy email blocks. Use `styles` for per-block background, background opacity, text color, padding, border radius, border width, and border color. Top-level style aliases such as `backgroundColor`, `backgroundOpacity`, `borderColor`, `borderWidth`, and `borderRadius` are also accepted and saved under `styles`. Use this for editor-compatible content, including conditional and repeat blocks. Repeat blocks use { type: 'repeat', source: 'items', itemAlias: 'item', children: [...] }.
promptNoGenerate campaign blocks from a prompt. Mutually exclusive with `html`, `blocks`, and `templateId`.
styleNoPrompt generation style: minimal, branded, promotional. Only used with `prompt`.
toneNoPrompt generation tone: professional, casual, friendly. Only used with `prompt`.
templateIdNoUse a template instead of html
segmentIdNoTarget segment ID
campaignDataNoOptional campaign-scoped JSON data for repeat blocks and personalization.
computedListsNoOptional computed list definitions derived from campaignData at send time.
labelsNoOptional label names to assign. Missing labels are created automatically.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the Sequenzy operation succeeded.
messageNoHuman-readable status, confirmation, or next-step message.
noteNoAdditional context about the result.
itemsNoFallback array wrapper used only when a tool returns a bare array.
valueNoFallback object wrapper used only when a tool returns a non-object value.
campaignNoThe campaign record returned by Sequenzy.
appUrlsNoDashboard URLs for relevant Sequenzy resources.
urlNoPrimary dashboard URL for this result.
settingsUrlNoCompany settings URL when available.
Behavior3/5

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

Annotations already indicate non-readOnly and non-destructive. The description adds the 'draft' status, which is a behavioral detail beyond annotations. However, it does not disclose other traits such as permissions needed, rate limits, or that the campaign is not immediately sent.

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?

The description is a single, efficient sentence with no wasted words. It is front-loaded with the action. However, given the tool's complexity, a slightly longer description could improve completeness without sacrificing conciseness.

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

Completeness2/5

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

Despite having an output schema and detailed parameter descriptions, the tool description is only one line. It does not explain what happens after creation, how to finalize the campaign, or handle errors. For a tool with many parameters and siblings, this is insufficient.

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 coverage is 100% with detailed descriptions for all 14 parameters. The tool description adds no additional semantics beyond the schema. Baseline of 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?

The description clearly states the tool creates a new campaign, with the qualifier '(as draft)' distinguishing it from update, duplicate, and other campaign operations. It is specific about verb and resource.

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?

No guidance is provided on when to use this tool versus siblings like duplicate_campaign or update_campaign. The description does not mention prerequisites, exclusions, or typical workflow context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sequenzy/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server