Skip to main content
Glama

Email Manage Tool

email_manage

Manage email themes and templates for FleetQ MCP server. Create, update, delete, and generate branded email designs with customizable colors, fonts, and layouts.

Instructions

Manage email themes and templates. Actions: theme_list, theme_get (theme_id), theme_create (name, styles), theme_update (theme_id + fields), theme_delete (theme_id), template_list, template_get (template_id), template_create (name, subject, body, theme_id), template_update (template_id + fields), template_delete (template_id), template_generate (prompt — AI generates template).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: theme_list, theme_get, theme_create, theme_update, theme_delete, template_list, template_get, template_create, template_update, template_delete, template_generate
statusNoFilter by status: draft, active, archived
limitNoMax results (default 10, max 100)
idYesEmail theme UUID
nameYesTheme name
primary_colorNoPrimary/CTA color as hex (e.g. #2563eb). Default: #2563eb
background_colorNoEmail background color as hex. Default: #f4f4f4
canvas_colorNoContent area background color as hex. Default: #ffffff
text_colorNoBody text color as hex. Default: #1f2937
heading_colorNoHeading text color as hex. Default: #111827
font_nameNoFont display name (e.g. Inter, Georgia). Default: Inter
font_urlNoGoogle Fonts or web font URL for @import
font_familyNoFull CSS font-family stack. Default: Inter, Arial, sans-serif
logo_urlNoAbsolute URL to the team logo image
email_widthNoMaximum email width in pixels. Default: 600
company_nameNoCompany name shown in email footer
company_addressNoCompany address shown in email footer
footer_textNoFooter text or HTML (e.g. unsubscribe line)
muted_colorNoMuted/secondary text color as hex
divider_colorNoDivider/border color as hex
heading_font_sizeNoHeading font size in pixels
body_font_sizeNoBody font size in pixels
logo_widthNoLogo width in pixels
content_paddingNoContent area horizontal padding in pixels
visibilityNoFilter by visibility: private, public
subjectNoEmail subject line
preview_textNoShort preview text shown in email clients
email_theme_idNoOptional email theme UUID to associate
html_bodyNoRaw HTML content. Stored directly as the template HTML.
mjml_bodyNoComplete MJML document starting with <mjml>. Compiled server-side to cross-client HTML. Preferred over html_body.
descriptionYesNatural language description of the email to generate, e.g. "Monthly newsletter with hero image, 3 product highlights, and a CTA button"
theme_idNoOptional email theme UUID. Brand colors, fonts, company name, and logo from the theme will be injected into the generated MJML.
toneNoWriting tone: professional, friendly, or minimal (default: professional)
Behavior2/5

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

Annotations are empty, so description carries full burden. Only behavioral hint is 'AI generates template' for template_generate. Missing: deletion permanence, generation latency, whether updates are atomic, compilation errors for MJML, or auth requirements. Note: Schema mentions server-side MJML compilation, but description ignores this.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single dense run-on sentence with 11 parenthetical clauses is hard to parse. Information density is high but poorly structured - no line breaks or grouping (themes vs templates). Every sentence earns its place, but the single sentence format hurts scannability.

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?

Complex 33-parameter multi-action tool with no output schema and no annotations. Description fails to explain relationships (themes contain templates), generation constraints, or error conditions. The required parameters array in schema appears incorrect (requires id/name/description for all actions), which description doesn't clarify.

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 has 100% description coverage with detailed field documentation (hex colors, defaults, format examples). Description adds minimal value by parenthetically indicating which actions use which parameters (e.g., 'theme_id + fields'), but this is redundant with schema. Baseline 3 is appropriate given schema completeness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb ('Manage') and resource ('email themes and templates'). Lists all 11 specific actions available, distinguishing it from sibling tools like 'outbound_manage' or 'integration_manage'. Deducted one point because it doesn't explain what themes vs templates are or when to use which.

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 on when to use this tool vs siblings (e.g., outbound_manage for sending vs this for designing). No indication of action dependencies (e.g., need theme before template_create). Simply enumerates actions without 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/escapeboy/agent-fleet-o'

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