Skip to main content
Glama
spruikco

send16-mcp

by spruikco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

design_email_template

Generate a complete HTML email template from a description. AI creates ready-to-use templates for marketing, transactional, or newsletter emails with custom styles and colors.

Instructions

Use AI to generate a complete email HTML template based on a description. Returns ready-to-use HTML that can be sent or used in campaigns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesType of email template to generate
styleYesVisual style/aesthetic for the template
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)
brandColorNoPrimary brand color as hex code (e.g. "#4F46E5")
companyNameNoCompany or brand name to include in the template
descriptionYesDetailed description of the email content and purpose (e.g. 'Welcome email for a SaaS product with feature highlights and CTA to start trial')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.7

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It states returns ready-to-use HTML but does not disclose side effects (e.g., does it save the template? Is it read-only?), API key usage beyond schema, or AI behavior. Minimal transparency.

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?

Single concise sentence with purpose and outcome. Front-loaded and efficient, no filler.

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

Completeness3/5

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

Tool has 6 parameters (3 required, enums) and no output schema. Description mentions 'ready-to-use HTML' but fails to clarify whether the generated template is persisted in the account, which is relevant given sibling tools for templates (get_template, list_templates). Could be more 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 description coverage is 100%, so each parameter has adequate description. The tool description adds no further meaning beyond what the schema provides (e.g., not explaining enum options or apiKey behavior). Baseline 3 applies.

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?

Description clearly states the tool generates a complete email HTML template from a description, using AI. It uses specific verb 'generate' and resource 'email HTML template', distinguishing it from siblings like send_email, render_email_content, and generate_email_from_url which focus on sending or rendering existing content.

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 explicit guidance on when to use this tool versus alternatives like generate_email_from_url or render_email_content. The description does not mention when not to use it or any prerequisites.

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

Deploy Server

Other Tools