AIsa Agent Mail

Inboxes - List Threads

get_agentmail_inbox_threads

Read-onlyIdempotent

List Threads

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

Input Schema

Name	Required	Description
`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.
`senders`	No	Filter to threads whose senders contain this value (substring match). Repeatable; all values must match.
`subject`	No	Filter to threads 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.
`recipients`	No	Filter to threads whose recipients contain this value (substring match). Repeatable; all values must match.
`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 / recipients

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

addedInput schema / properties / senders

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

addedInput schema / properties / subject

Added value: +{
+  "description": "Filter to threads whose subject contains 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 / recipients

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

removedInput schema / properties / senders

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

removedInput schema / properties / subject

Removed value: -{
-  "description": "Filter to threads whose subject contains 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 / recipients

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

addedInput schema / properties / senders

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

addedInput schema / properties / subject

Added value: +{
+  "description": "Filter to threads whose subject contains 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.1/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 fully covered by structured data. The description adds only a pricing note, which is cost context rather than behavioral disclosure about filtering, pagination, or result scope.

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

Conciseness3/5

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

The text is short and the purpose line is front-loaded, but the only substantive content is an HTML-commented pricing boilerplate block, so the brevity reflects a lack of information rather than efficient editing.

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?

An output schema exists and annotations cover safety, but for a 14-parameter listing tool the description offers no explanation of filtering semantics, spam/trash/blocked inclusion behavior, or how this differs from the global thread-listing sibling, leaving an agent without routing guidance.

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 already documents each filter, sort, and pagination option thoroughly, establishing the baseline of 3. The description contributes nothing beyond the schema for any parameter.

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?

The description is 'List Threads', which merely restates the title 'Inboxes - List Threads' with no additional detail. It does state a verb+resource, but it does not distinguish this inbox-scoped thread listing from siblings such as get_agentmail_threads or get_agentmail_inbox_messages, so it reads as a tautology rather than an explanation.

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

Usage Guidelines1/5

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

There is no usage guidance whatsoever: no statement of when to prefer this inbox-scoped listing over get_agentmail_threads, no prerequisites, and no mention of the 14 filtering options available.

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?