Skip to main content
Glama
Sequenzy

Sequenzy MCP Server

Official

create_template

Create email templates with custom subject, HTML content or blocks, and optional labels. Streamline email marketing by building reusable templates.

Instructions

Create a new email template

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdNoCompany ID. If not provided, uses the currently selected company.
nameYesTemplate name
subjectYesEmail subject line
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: [...] }.
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.
templateNoThe email template 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 it is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description does not add any behavioral details beyond the annotations, such as side effects, permissions, or return behavior. It is adequate but not enhanced.

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 a single concise sentence that immediately conveys the tool's purpose. It is front-loaded with the verb and resource, with no extraneous words or repetition.

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 moderate complexity (6 params, 2 required), the presence of full schema descriptions and an output schema, the description is sufficient. It could optionally mention the company context or the html/blocks distinction, but the schema handles that adequately.

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?

The input schema provides detailed descriptions for all 6 parameters (100% coverage). The description does not add any extra meaning or context about parameters beyond what the schema already states. Baseline score 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 action 'Create' and the resource 'new email template'. It is specific and distinct from sibling tools like update_template, delete_template, and list_templates.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., create_transactional_email). It lacks context about prerequisites, when not to use, or what to consider before creating a template.

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