Skip to main content
Glama
agentisend

agentisend

Get email events

get_email_events
Read-onlyIdempotent

Retrieve every event recorded for one sent email, ordered oldest first, with provider details and cursor pagination so you can inspect exactly what happened to that message.

Instructions

Purpose: read every event recorded for one sent message, oldest first, with the provider detail. NOT for: deciding what to do about a bounce (explain_email) or counting across many messages (get_metrics). Returns: data, has_more, and next_cursor. Each row has type, occurred_at, recipient, detail and provider_message_id.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (1-200).
cursorNonext_cursor from the previous page. Omit for the first page.
email_idYesThe message id returned by send_email.

Output Schema

NameRequiredDescriptionDefault
dataNoThis page of rows.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
has_moreNoTrue when another page follows.
next_cursorNoPass back as cursor for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the deterministic ordering and pagination behavior (has_more/next_cursor). It stops short of stating what happens with unknown email_ids or how long events are retained, so it is strong but not exhaustive.

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?

Three labeled, front-loaded segments (Purpose / NOT for / Returns) with no filler. Every sentence contributes either routing or output shape.

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 read-only paged list tool with an output schema present, the definition covers scope, ordering, exclusions, and paging. Nothing needed to invoke it correctly is missing; the Returns line is mildly redundant with the output schema but harmless.

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%, so email_id, limit, and cursor are already documented, and the description adds nothing parameter-specific beyond implying pagination through next_cursor. Baseline 3 applies since the schema carries the load.

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 every event recorded for one sent message') plus ordering ('oldest first') and a distinguishing scope limit. It explicitly separates itself from explain_email and get_metrics, so an agent can pick it without comparing schemas.

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 two concrete alternatives and the conditions that select them (bounce decisions, cross-message counting). The positive case, per-message event history, is stated in the same breath.

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