Skip to main content
Glama

Hail Communication for AI

Get email events

get_email_events
Read-onlyIdempotent

Read one email's delivery and engagement timeline.

    Events include sent, delivered, delivery_delayed, bounced, complained,
    rejected, opened and clicked, with ``payload`` and ``occurred_at``.
    Open and click events require an HTML email body.
    Returns ``items`` and ``next_cursor``, or an error.

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
limitNoHow many items one page holds. ``next_cursor`` in the response points to the next page. Omitted: the API returns 100.
cursorNoPagination cursor: the ``next_cursor`` from the previous page. Omitted: the first page.
email_idYesEmail ID, from ``send_email`` or ``list_emails``.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of items per page. Omitted: 100."New value: +"How many items one page holds. ``next_cursor`` in the response points to the next page. Omitted: the API returns 100."
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 1000,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / limit / description
      Previous value: -"Page size, 1 to 1000. Omitted: 100."New value: +"Number of items per page. Omitted: 100."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds real behavioral context beyond that: the exact event taxonomy, the caveat that open and click events require an HTML email body, and the error possibility. That HTML-body prerequisite is the kind of non-obvious constraint an agent could not get from the annotations.

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?

Four short lines, front-loaded with the core action, then scope, then caveats. Every sentence carries information; the only minor waste is restating the return envelope, which the output schema already covers.

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 list tool with a full output schema and complete parameter documentation, the description supplies what structured fields cannot: the event taxonomy and the HTML-body prerequisite. Nothing an agent needs in order to call it correctly is missing, other than sibling disambiguation, which is scored elsewhere.

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 description coverage is 100%, and the schema already explains email_id provenance, limit defaults, and cursor semantics. The description adds no parameter-level meaning of its own, so the baseline 3 applies.

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?

States a specific verb and resource: 'Read one email's delivery and engagement timeline.' It then enumerates the event types, which makes the resource scope concrete. It does not, however, distinguish itself from the sibling get_events or explain how it differs from get_email_stats, so an agent must infer the boundary.

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?

Usage is only implied by the phrase 'one email's' – the scoping hint suggests use when you have a single email_id, and the sibling get_events presumably covers broader event queries. There is no explicit when-to-use or when-not-to-use guidance and no named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources