Skip to main content
Glama
agentisend

agentisend

Get email

get_email
Read-onlyIdempotent

Retrieve a sent email by ID with its message details and ordered event timeline—queued, sent, delivered, bounced, or complained—to inspect delivery status.

Instructions

Purpose: read one message you sent, with its event timeline — queued, sent, delivered, bounced, complained. NOT for: working out what to DO about a bounce (explain_email), or finding an id (list_emails). Returns: the same message GET /emails/:id returns (from, to, cc, bcc, subject, html, text, tags, status, created_at and the rest), plus events in order. not_found means the id is not one of this account's; it is not retryable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email_id": "<email_id>"
    },
    "name": "get_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYesThe message id returned by send_email.

Output Schema

NameRequiredDescriptionDefault
idNoIdentifier.
toNoThe recipients.
fromNo
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
statusNo
subjectNo
created_atNoISO 8601 time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description goes further by disclosing that the response is the message record plus an ordered event timeline and by spelling out the error semantics of not_found. That error behavior (non-retryable, account-scoped) is information no structured field carries.

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?

Uses front-loaded Purpose / NOT for / Returns labels, so an agent can stop reading as soon as it has what it needs. Every sentence carries distinct information: scope, exclusions, payload, and error semantics; no filler.

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

Completeness5/5

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

For a single-parameter read tool with an output schema and full annotations, nothing needed to call it correctly is missing. The description even enumerates the return shape despite an output schema existing, and closes the error-handling gap that the schema and annotations do not cover.

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?

Only one parameter and schema description coverage is 100% — the schema already documents email_id as the message id returned by send_email, including a UUID pattern. The description only indirectly reinforces that the id must belong to a sent message in this account. Per the high-coverage baseline, 3 is appropriate.

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?

States a specific verb and resource ('read one message you sent, with its event timeline') and immediately contrasts itself with the two siblings an agent might confuse it with (explain_email, list_emails). The scope restriction to outbound sent messages is explicit, which also distinguishes it from get_received_email among the siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'NOT for' clause names both alternative tools and the condition that selects each one — debugging a bounce goes to explain_email, id lookup goes to list_emails. It also states the operational rule for the not_found case (id not in this account, not retryable), which is exactly the guidance an agent needs to avoid a retry loop.

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