Skip to main content
Glama
dipseth

google-workspace-unlimited

Compose Dynamic Email

compose_dynamic_email

Compose responsive HTML emails using a DSL that defines block structure for hero, text, button, and other components.

Instructions

Compose responsive HTML emails using DSL notation for block structure. Common patterns: ε[ħ, τ] = hero + text, ε[ħ, τx2, Ƀ] = hero + 2 text blocks + button. DSL structure using symbols. Symbols: ε=EmailSpec, ħ=HeroBlock, τ=TextBlock, Ƀ=ButtonBlock, ɨ=ImageBlock, ¢=ColumnsBlock, ©=Column, Ħ=HeaderBlock, ƒ=FooterBlock, ą=AccordionBlock, ȼ=CarouselBlock. Read skill://mjml-email/ for full reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNo
toNomyself
bccNo
actionNo'draft' (default, safe) or 'send' to deliver immediatelydraft
email_paramsNoREQUIRED for content — all block text/titles/URLs go here, keyed by symbol or class name. Example: {"ħ": {"title": "Welcome!", "subtitle": "Hi there"}, "τ": {"_items": [{"text": "Your message here"}]}, "Ƀ": {"_items": [{"text": "Click", "url": "https://..."}]}}. Also accepts 'subject' and 'preheader' keys.
email_descriptionYesONLY the DSL structure + email subject line. Format: 'ε[ħ, τ] My Subject Here'. Do NOT put block content here — use email_params for that. Examples: 'ε[ħ, τ] Welcome aboard', 'ε[ħ, τx2, Ƀ] Monthly Newsletter'. Text after the DSL becomes the email subject (keep it short). DSL structure using symbols. Symbols: ε=EmailSpec, ħ=HeroBlock, τ=TextBlock, Ƀ=ButtonBlock, ɨ=ImageBlock, ¢=ColumnsBlock, ©=Column, Ħ=HeaderBlock, ƒ=FooterBlock, ą=AccordionBlock, ȼ=CarouselBlock. Read skill://mjml-email/ for full reference.
user_google_emailNoUse 'me' or 'myself' for auto-resolution to authenticated user, or provide specific email address. If None, uses current authenticated user (auto-injected by middleware).
Behavior3/5

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

Annotations indicate readOnlyHint=false, which is consistent with composing emails. The description discloses that the action parameter defaults to 'draft' (safe) and can be set to 'send' for immediate delivery, which adds behavioral context. However, it does not discuss error handling, rate limits, or side effects beyond creation.

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 concise, with key information front-loaded. The symbol list is repeated in both the main description and the email_description parameter, introducing minor redundancy, but overall it is efficient and well-structured.

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 complexity of the DSL and the absence of an output schema, the description provides adequate context for using the tool. It points to a skill reference for full details and covers the essential aspects. However, it could briefly mention what the tool returns (e.g., email ID).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds value beyond the input schema by explaining the DSL structure for email_description and providing detailed examples for email_params. It clarifies the action parameter options and user_google_email resolution. With 57% schema coverage, the description compensates well for undocumented 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 the tool's purpose: composing responsive HTML emails using a specific DSL notation. It provides common patterns and lists all symbols, distinguishing it from other email-related tools like draft_gmail_message or send_gmail_message.

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 gives examples and mentions a skill reference for full details, but it does not explicitly state when to use this tool versus alternatives, nor does it provide 'when-not' scenarios. Usage guidance is implied but not fully explicit.

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/dipseth/google_workspace_fastmcp2'

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