Skip to main content
Glama
agentisend

agentisend

List received emails

list_received_emails
Read-onlyIdempotent

Read incoming mail for an account's domains, newest first, and filter by recipient, sender, or search string. Each result includes a clear, review, or unavailable verdict and reasons.

Instructions

Purpose: read mail that arrived at this account’s domains, newest first. Filter by recipient, sender, or a search string. Each row carries verdict (clear, review, or unavailable) and the reasons. Held messages are left out unless include_held is true. A held message is waiting for a person to release it; it is not in the arrival webhook yet. NOT for: mail you sent (list_emails), grouping a conversation (list_threads), or sending a reply (reply_to_email). Returns: data, has_more, and next_cursor. Page again by passing next_cursor as cursor; when has_more is false you have everything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_received_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch the subject, either address, or the start of the message id.
toNoOnly mail delivered to this address.
fromNoOnly mail from this address.
limitNoPage size (1-100).
sinceNoOnly mail received at or after this instant (ISO-8601 with an offset).
untilNoOnly mail received at or before this instant (ISO-8601 with an offset).
cursorNonext_cursor from the previous page. Omit for the first page.
include_heldNoSet true to include messages a person has not released yet. Omitted, those messages are left out.

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.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the lower bar applies; the description nonetheless discloses non-obvious behavior: held messages are silently excluded by default, and a held message is defined as one awaiting manual release that is not yet in the arrival webhook. It also surfaces the verdict/reasons column and the pagination termination condition.

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?

Labeled sections (Purpose, Held, NOT for, Returns) front-load the scoping constraint and pagination rule. Every sentence carries information an agent needs; nothing is redundant padding.

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?

Despite 8 parameters, the definition covers default filtering behavior, exclusion semantics, pagination flow and return shape. With an output schema present, the brief 'Returns' line is sufficient rather than required, and no agent decision is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 is the baseline; the description earns an extra point by explaining the include_held trade-off and the cursor-to-next_cursor paging loop, which the schema only states mechanically. It does not add format detail for since/until or q beyond what the schema already documents.

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?

The description opens with a specific verb and resource ('read mail that arrived at this account's domains'), adds ordering ('newest first'), and names exactly the sibling tools it is not (list_emails, list_threads, reply_to_email). An agent can distinguish it from get_received_email by scope alone.

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?

It gives an explicit 'NOT for' block pairing each excluded use case with the correct alternative tool, and states the condition that changes behavior (include_held true). No inference is required to choose between this and its siblings.

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