Skip to main content
Glama

inboxmcp

by io.github.zhlei07
OverviewDiscussionsAdmin

List incoming email events

list_email_events
Read-onlyIdempotent

Browse incoming email (sender, subject, time) when the user asks what arrived or who wrote.

    Requires email:read. Returns events with message IDs, sender/subject metadata and legacy decisions,
    oldest first with next_cursor, or newest first with next_before when newest_first is true. Use
    get_email_context for a listed event's body. For recurring monitoring use claim_email_batch instead:
    this listing does not save progress, and a recorded legacy decision does not mean this connection
    has processed the email.

Input Schema

NameRequiredDescriptionDefault
afterNoExclusive event cursor, zero or greater. Only events newer than it are listed. In oldest-first order pass next_cursor from the previous page; 0 starts at the oldest retained event.
limitNoMaximum number of events to return, from 1 to 100; default 50.
beforeNoWith newest_first: exclusive upper cursor; pass next_before from the previous page. 0 starts at the newest event.
newest_firstNoList the most recent email first, for questions like 'what came in today?' or 'did X write?'. Page further back with next_before.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / after / description
      Previous value: -"Exclusive event cursor, zero or greater. Use next_cursor from the previous page; 0 starts at the oldest retained event."New value: +"Exclusive event cursor, zero or greater. Only events newer than it are listed. In oldest-first order pass next_cursor from the previous page; 0 starts at the oldest retained event."
    • addedInput schema / properties / before
      Added value: +{
+  "default": 0,
+  "description": "With newest_first: exclusive upper cursor; pass next_before from the previous page. 0 starts at the newest event.",
+  "title": "Before",
+  "type": "integer"
+}
    • addedInput schema / properties / newest_first
      Added value: +{
+  "default": false,
+  "description": "List the most recent email first, for questions like 'what came in today?' or 'did X write?'. Page further back with next_before.",
+  "title": "Newest First",
+  "type": "boolean"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / after / description
      Added value: +"Exclusive event cursor, zero or greater. Use next_cursor from the previous page; 0 starts at the oldest retained event."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of events to return, from 1 to 100; default 50."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description still adds real context beyond them: the required email:read scope, the ordering and cursor semantics of the result set, and the non-obvious caveat that a recorded legacy decision does not imply this connection processed the email.

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?

Front-loaded with purpose and alternatives, and each sentence carries distinct information (permission, return shape, paging, hand-off, caveat). The middle block is dense and could be split for scanability, but there is 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?

There is no output schema, so the description correctly carries the return contract (message IDs, sender/subject metadata, legacy decisions, next_cursor / next_before paging) along with the auth requirement. Nothing an agent needs to call this correctly is missing.

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%, so all four parameters (after, limit, before, newest_first) are already fully documented in the schema, including which cursor to pass for each direction. The description reinforces the directional paging model but adds no syntax or constraints beyond what the schema states, so the 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?

Opens with a specific verb+resource ('Browse incoming email') and scopes it with a parenthetical of the fields returned plus the user intent it serves. It also names the sibling it is not ('Use get_email_context for a listed event's body', 'for recurring monitoring use claim_email_batch instead'), so an agent can route without opening a schema.

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?

States the triggering condition ('when the user asks what arrived or who wrote') and two explicit alternatives with their own conditions. It goes further by naming when-not: recurring monitoring belongs to claim_email_batch because 'this listing does not save progress'.

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

All inboxmcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources