Skip to main content
Glama
agentisend

agentisend

List emails

list_emails
Read-onlyIdempotent

Find email messages newest first, filtering by status, sender, recipient, tag, domain, date, or search term; use cursor paging to retrieve all matching results.

Instructions

Purpose: find messages, newest first. Filter by status, sender, recipient (to, cc or bcc), tag, domain or a search string — the same filters GET /emails takes. NOT for: analytics or counting — it pages rows, it does not aggregate. 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_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch the subject, a recipient, or the start of the message id.
toNoOnly mail whose to, cc or bcc contains this address.
tagNoname:value, for example campaign:welcome. Only mail carrying that tag.
fromNoOnly mail from this address. The display name is ignored.
limitNoPage size (1-100).
sinceNoOnly mail created at or after this instant (ISO-8601).
untilNoOnly mail created at or before this instant (ISO-8601).
cursorNonext_cursor from the previous page. Omit for the first page.
domainNoOnly mail sent from this domain.
statusNoOnly return emails in this state.

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

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is low, yet the description still adds real behavioral contract: sort order (newest first), the paging model via next_cursor, and the terminal condition ('when has_more is false you have everything'). That pagination guidance is exactly the kind of context annotations cannot express.

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?

Three labeled sentences (Purpose / NOT for / Returns) with zero filler and the core purpose front-loaded. Each sentence earns its place by covering a distinct concern.

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 paged read tool with full annotations, complete schema coverage, and an output schema, this covers everything an agent needs: what it fetches, what it excludes, and how to iterate pages. Nothing material 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 the schema already documents all ten parameters including the limit range, ISO-8601 formats, and the name:value tag syntax. The description only summarizes the filter set and clarifies 'to' covers to/cc/bcc, adding little beyond the schema. Baseline 3 is correct.

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 ('find messages, newest first') and enumerates the filter axes (status, sender, recipient, tag, domain, search string), tying them to GET /emails. It routes away from analytics/counting, but does not distinguish itself from the genuinely confusable list_received_emails sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'NOT for: analytics or counting' clause is an explicit when-not, and the filter list defines when this tool applies. It falls short of a perfect score because it never names the alternative tool an agent should use for aggregation or for received mail.

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