Skip to main content
Glama
OpenInbox – Email for AI Agents

OpenInbox – Email for AI Agents

Official

List emails

list_emails
Read-only

List recent inbox emails newest first, with sender, subject, preview and detected verification codes. Filter unread only to find messages needing action.

Instructions

List the emails in an inbox (newest first, up to 30) with sender, subject, preview and detected codes.

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": {
      "inbox_id": "<inbox_id>"
    },
    "name": "list_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_idYesThe inbox_id returned by create_inbox.
unread_onlyNoOnly return unread emails.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral facts the annotations do not: results are ordered newest first, capped at 30, and include auto-detected codes in each message. What it omits is whether that 30-item cap is a hard truncation with no way to page further.

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?

A single sentence with no waste, front-loading the core action and folding ordering, limit, and return shape into a compact parenthetical. Every clause carries information an agent would otherwise have to discover by calling the tool.

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

Completeness4/5

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

For a simple two-parameter read tool with annotations covering the safety profile and full schema coverage, the description is nearly sufficient, and listing the returned fields compensates for the absent output schema. The remaining gap is pagination behavior: an agent cannot tell from this text whether 30 results means the inbox is exhausted or truncated.

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 both parameters (inbox_id and unread_only) are already documented in the schema. The description adds no further meaning to either — it never mentions the unread filter or explains how inbox_id relates to create_inbox — so the baseline of 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?

The description gives a specific verb and resource ("List the emails in an inbox") and adds scope detail: newest-first ordering, a 30-item cap, and the fields returned (sender, subject, preview, detected codes). That is enough to distinguish it from read_email, which presumably returns full message content, though the description never names that sibling.

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 implied by the phrase "List the emails in an inbox" and the preview-level return fields suggest a triage/scan use case, but there is no explicit guidance on when to prefer this over read_email or wait_for_email, and no stated prerequisites beyond the schema's inbox_id.

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