ReviseMy Try with your agent

Built for Email

Email design review at inbox width

Agents paste HTML; ReviseMy renders at ~600px. Mark the dominant CTA, dark-mode risks, and footer compliance — then loop until a human approves send.

The problem

Email gets coded by agents who optimize for modern CSS, not Outlook tables. Feedback lives in forwarded threads with no region-level marks, and nobody checks dark mode or unsubscribe footer until post-send.

How ReviseMy fits

Your agent opens a review with `type: email` so hints cover CTA, dark mode, images-off, and footer rules. Prefer pasting HTML for an inbox-width render; screenshots of Litmus/Email on Acid previews work too.

Review type: email · Exactly one ingest source per review

How to get pixels in

Review type chooses the email lens. Ingest chooses how the message is rendered. Use exactly one source per call — HTML is ideal, but screenshots and other sources still get the email checklist when you set the type.

Email HTML

html Recommended

Best default. Pass raw HTML; ReviseMy renders at ~600px like a mail client and defaults to `type: email`.

Screenshots

images

Client previews, dark-mode screenshots, or images-off renders from a testing tool. Set `type: email` so hints stay email-specific.

Live URL capture

capture_url

Hosted HTML preview URL (public). Capture with `capture_url` and set `type: email` — useful when the template is served as a page.

PDF pages

pdf

Design comps of the email exported as PDF. Pair with `type: email` when you want CTA/footer hints on the mock, not the slide deck checklist.

Features for email review

Rendered at ~600px

Review what recipients see — single-column inbox width, not a full browser canvas stretched wide.

CTA, dark mode, and footer lens

Email checklists stress one dominant action, dark-mode color flips, images-off fallback, and legal footer requirements — the gaps screenshots alone cannot catch.

Region marks on the template

Outline the hero, CTA block, or footer directly on the render so agents know exactly which table cell or section to fix.

Human sign-off before send

Structured `next_action` keeps agents from marking an email “done” until you approve. Multi-pass with parent reviews for template iterations.

Email checklist

ReviseMy runs these checks as optional second-opinion hints. Your marks stay authoritative.

  • One dominant CTA — secondary links defer visually
  • Subject and preheader written and complementary (not in the PNG)
  • Dark mode: logos, borders, and pure-black text when colors invert
  • Images-off: key content and CTA survive with images blocked
  • Footer: unsubscribe link, physical address, sender identity

Sample prompts

Try saying these to your agent after connecting MCP from the homepage.

  • “Review this email HTML before we send — share the review link.”
  • “Run a design checkup on the newsletter template.”
  • “Fix my email marks and attach after renders when you resolve each one.”

FAQ

How do I submit email HTML?

Pass the HTML string to `create_review` with `type: email` (the default when using `html`). ReviseMy renders it server-side at roughly inbox width.

Can I review screenshots from email testing tools?

Yes. Pass them as `images` with `type: email`. Handy for Outlook or dark-mode previews the HTML renderer cannot fully reproduce.

Does ReviseMy test every email client?

No — it renders for human review with an email-specific checklist. Implement with table-based, ~600px layouts for Outlook and other clients.

Can vision models review the email?

Optional Claude or OpenAI vision can add region hints when configured. Hints are suggestions only; your marks stay authoritative.

Other review types

Try with your agent