AIsa Agent Mail

Inboxes - List Messages

get_agentmail_inbox_messages

Read-onlyIdempotent

List Messages

Published reference price: $0.012 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

Name	Required	Description
`to`	No	Filter to messages whose recipients (to, cc, or bcc) contain this value (substring match). Repeatable; all values must match.
`from`	No	Filter to messages whose sender contains this value (substring match). Repeatable; all values must match.
`after`	No	Timestamp after which to filter by.
`limit`	No	Limit of number of items returned.
`before`	No	Timestamp before which to filter by.
`labels`	No	Labels to filter by.
`subject`	No	Filter to messages whose subject contains this value (substring match). Repeatable; all values must match.
`inbox_id`	Yes	The ID of the inbox.
`ascending`	No	Sort in ascending temporal order.
`page_token`	No	Page token for pagination.
`include_spam`	No	Include spam in results.
`include_trash`	No	Include trash in results.
`include_blocked`	No	Include blocked in results.
`include_unauthenticated`	No	Include unauthenticated in results.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 15, 2026

removedInput schema / properties / Authorization

Removed value: -{
-  "description": "Bearer authentication",
-  "type": "string"
-}

addedInput schema / properties / from

Added value: +{
+  "description": "Filter to messages whose sender contains this value (substring match). Repeatable; all values must match.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / subject

Added value: +{
+  "description": "Filter to messages whose subject contains this value (substring match). Repeatable; all values must match.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "Filter to messages whose recipients (to, cc, or bcc) contain this value (substring match). Repeatable; all values must match.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "inbox_id",
-  "Authorization"
-]New value: +[
+  "inbox_id"
+]

Changed5 schema fields changedOct 15, 2026

addedInput schema / properties / Authorization

Added value: +{
+  "description": "Bearer authentication",
+  "type": "string"
+}

removedInput schema / properties / from

Removed value: -{
-  "description": "Filter to messages whose sender contains this value (substring match). Repeatable; all values must match.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / subject

Removed value: -{
-  "description": "Filter to messages whose subject contains this value (substring match). Repeatable; all values must match.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / to

Removed value: -{
-  "description": "Filter to messages whose recipients (to, cc, or bcc) contain this value (substring match). Repeatable; all values must match.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

changedInput schema / required

Previous value: -[
-  "inbox_id"
-]New value: +[
+  "inbox_id",
+  "Authorization"
+]

Changed5 schema fields changedOct 15, 2026

removedInput schema / properties / Authorization

Removed value: -{
-  "description": "Bearer authentication",
-  "type": "string"
-}

addedInput schema / properties / from

Added value: +{
+  "description": "Filter to messages whose sender contains this value (substring match). Repeatable; all values must match.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / subject

Added value: +{
+  "description": "Filter to messages whose subject contains this value (substring match). Repeatable; all values must match.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "Filter to messages whose recipients (to, cc, or bcc) contain this value (substring match). Repeatable; all values must match.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "inbox_id",
-  "Authorization"
-]New value: +[
+  "inbox_id"
+]

First observedSep 15, 2026

TDQS

C2.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing behavioral about the tool itself — no pagination behavior, no default filtering (e.g., whether spam/trash are excluded by default), no result ordering — only a billing note.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but shortness here reflects under-specification rather than efficiency. The embedded pricing HTML comment block is boilerplate noise that consumes most of the text without describing the tool.

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

Completeness2/5

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

For a 14-parameter filtered list tool with rich pagination and include_* semantics, the description supplies none of the context an agent needs about defaults or scope, relying entirely on the schema and annotations. The existence of an output schema excuses omitting return values, but not omitting usage and default-filtering context.

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% across all 14 parameters, so the schema fully documents filters such as to/from/subject, date bounds, and the include_* flags. The description adds no additional meaning beyond the schema, which is the expected baseline of 3 when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List Messages" merely restates the tool title ("Inboxes - List Messages") without stating scope, what an inbox message is, or how it differs from siblings like get_agentmail_inbox_threads or get_agentmail_inbox_message. It is a tautological restatement rather than a description of what the tool does.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no condition for choosing this over thread- or message-level siblings, and no mention of prerequisites. The only additional sentence is a pricing disclaimer, which does not help an agent decide whether to invoke the tool.

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

All AIsa Agent Mail tools Inspect

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

Need Help?