AIsa Agent Mail

List Threads

get_agentmail_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.
`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: -[
-  "Authorization"
-]New value: +[]

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: -[]New value: +[
+  "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: -[
-  "Authorization"
-]New value: +[]

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. The description contributes no additional behavioral context — no pagination behavior, no default filter state, no scope/auth notes — only a generic per-request price that is not tool-specific.

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 the content does not earn its place: one line repeats the title and the other is an HTML-commented pricing block that aids neither selection nor invocation. There is no front-loaded scoping or filtering information to orient the agent.

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 13-parameter listing tool with many near-identical siblings, the description omits the one thing an agent cannot infer from the schema: which threads are listed (all inboxes? a scoped set?) and how this differs from get_agentmail_inbox_threads. The output schema does cover return values, so that gap is excused, but the scope ambiguity remains.

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 13 parameters (each has a description covering date filters, substring-match semantics, repeatability, pagination token, and include_* flags), so the baseline of 3 applies. The description adds no parameter meaning of its own, neither compensating nor detracting.

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 body is literally 'List Threads', an exact restatement of the tool title, which the rubric classifies as tautology. It gives no verb+resource specificity beyond the name and does nothing to separate this tool from close siblings such as get_agentmail_inbox_threads, get_agentmail_inbox_thread, or get_agentmail_thread.

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 at all: no scope statement (all inboxes vs. a specific inbox), no mention of when to prefer this over get_agentmail_inbox_threads, and no exclusions. The only sentence present besides the title is a pricing boilerplate note, which does not help selection.

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?