Skip to main content
Glama
Sequenzy

Sequenzy MCP Server

Official

get_email_send

Read-only

Retrieve a sent email by ID, including its HTML body and event timeline. Returns a sparse summary if the email row has been cleaned up.

Instructions

Get a sent email by emailSendId, including the stored HTML body when available and the ClickHouse event timeline. If the short-lived email send row has been cleaned up, returns the retained ClickHouse events and a sparse summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdNoCompany ID. If not provided, uses the currently selected company.
emailSendIdYesEmail send ID to inspect.

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.
emailSendNoThe email send 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 declare read-only and non-destructive behavior. The description adds valuable context about the HTML body availability, event timeline inclusion, and handling of cleaned-up rows, which is beyond annotations.

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?

Two concise sentences that efficiently convey purpose, scope, and edge-case behavior without redundancy.

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 presence of an output schema and high schema coverage, the description effectively covers purpose, edge cases, and return content. A small improvement would be to note when to prefer this over other get tools.

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% and both parameter descriptions are already complete. The description adds no new semantic information beyond what the schema provides.

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?

The description clearly states the tool retrieves a sent email by ID, including HTML body and event timeline. It is specific and actionable, but does not explicitly differentiate from sibling tools like get_transactional_email.

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?

No explicit guidance on when to use this tool versus alternatives. The context of inspecting sent emails is implied but not directly compared to other get_* tools.

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