Skip to main content
Glama

Deliveries Emails Events

deliveries_emails_events

Retrieve email delivery events for a specific email to track status, failures, and history; pass filters, sorting, pagination, and field selection via query parameters.

Instructions

Get a collection of email events. GET /organisations/{organisationId}/deliveries/emails/{emailId}/events

Extra query parameters (language, sort, filter, q, include, fields[...]) pass through verbatim via query.

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": {
      "organisation_id": "<organisation_id>",
      "email_id": "<email_id>"
    },
    "name": "deliveries_emails_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
email_idYes
page_limitNo
page_numberNo
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; 'Get a collection' at least signals a read operation and the endpoint path implies a nested resource lookup. It says nothing about pagination behavior, rate limits, permissions, or what an event record contains, leaving real gaps for a mutation-free but non-trivial tool.

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?

Two short sentences, front-loaded with the purpose before the implementation detail. The raw path template is somewhat redundant given the schema, but it is compact and does not bury the main point.

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

Completeness3/5

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

For a read-only collection tool with no output schema and zero schema description coverage, the definition is minimally sufficient: purpose and query pass-through are covered. It stops short of explaining the two pagination parameters or the shape/sorting defaults of the returned event collection.

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 0% across 5 parameters, and the description compensates partially: it maps organisation_id and email_id to the path template and enumerates the pass-through query keys (language, sort, filter, q, include, fields) that the schema types only as a string map. page_limit and page_number remain completely undocumented in both places.

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 states a specific verb and resource ('Get a collection of email events') and pins it to a concrete endpoint scoped by organisation and email id. That distinguishes it from siblings like deliveries_emails_show (single email) or deliveries_emails_events_image, though no sibling is named explicitly.

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: fetch the event history for a given email delivery. There is no statement of when to prefer this over deliveries_emails_show or deliveries_ebills_events, and no prerequisites or exclusions are given.

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