Skip to main content
Glama
Sequenzy

Sequenzy MCP Server

Official

create_landing_page

Create a draft landing page for email marketing campaigns using custom content or a starter template from available options.

Instructions

Create a draft landing page. Provide content for an exact page, or a template for generated starter content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdNoCompany ID to create the landing page in. If not provided, uses the currently selected company.
nameNoLanding page name. Optional; defaults to a template-specific name.
slugNoOptional URL slug. It will be normalized and made unique within the company.
templateNoOptional template key for default content, such as from-scratch, waitlist, lead-magnet, launch, demo-request, webinar, newsletter, product-hunt, pricing-offer, agency-lead-gen, or feature-announcement.
contentNoComplete Sequenzy landing page content JSON. Use this when replacing the page structure. The content must be the editor-compatible landing page schema with version, template, seo, theme, and blocks. Landing pages must include exactly one footer block and at most one form block.

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.
landingPageNoThe landing page record returned by Sequenzy.
appUrlsNoDashboard URLs for relevant Sequenzy resources.
urlNoPrimary dashboard URL for this result.
settingsUrlNoCompany settings URL when available.
Behavior4/5

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

Annotations already indicate it's not read-only, and the description adds that it creates a draft. No contradiction; it adequately discloses the creation behavior without needing to detail every side effect.

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, front-loaded sentence with no wasted words. It efficiently conveys the core functionality.

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 good schema coverage and an output schema, the description covers the main purpose and modes. It could mention the output schema, but that is already provided separately, making it fairly complete.

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%, so the description's addition of 'exact page' vs 'starter content' is useful but minimal. Baseline 3 is appropriate as the schema already explains parameters.

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 'Create a draft landing page' and distinguishes two modes: exact content or template-based. This differentiates it from sibling tools like publish_landing_page or update_landing_page.

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

Usage Guidelines3/5

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

The description implies when to use content vs template but does not explicitly state when not to use this tool or alternatives. No prerequisites or use cases are mentioned.

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