Fluxmail

search_emails_batch

Read-only

Search up to 20 email accounts at once with one portable query and return one result group per account, with filters for dates, folders, read status, attachments, and snippets.

Instructions

Search up to 20 accounts with one portable query and return one result group per account.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No
`from`	No
`read`	No
`after`	No	YYYY-MM-DD received date, inclusive in UTC
`query`	Yes	Typed portable search syntax
`before`	No	YYYY-MM-DD received date, exclusive in UTC
`folder`	No
`starred`	No
`subject`	No
`accounts`	Yes
`pageSize`	No	Defaults to 25
`hasAttachment`	No
`includeSnippet`	No	Request or suppress message previews
`includeSearchContext`	No	Include a match-centered body excerpt; requires a portable text query

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.1Oct 1, 2026
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```

Changed1 schema field changedv0.11.0Sep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "properties": {
+        "exhausted": {
+          "type": "boolean"
+        },
+        "groups": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "accountId": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "accountId"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "groups",
+        "exhausted"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.10.0Sep 23, 2026

addedInput schema / properties / includeSearchContext

Added value: +{
+  "description": "Include a match-centered body excerpt; requires a portable text query",
+  "type": "boolean"
+}

Addedv0.9.0Sep 16, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, so safety is covered. The description usefully adds that results are grouped per account with a shared query, but says nothing about pagination, page-token behavior across accounts, or rate limits for a 20-account fan-out.

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

Conciseness4/5

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

A single tightly written sentence with no filler, front-loading the batch scope and grouping behavior. It is efficient, though arguably too terse for a 14-parameter 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?

Output schema exists so return values need not be described, but for a 14-param, 43%-covered tool with nested account/pagination semantics, the one-line description leaves the agent without enough guidance on filters, pagination, or multi-account error handling.

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

Parameters2/5

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

Schema description coverage is only 43% across 14 parameters, and the description adds meaning for just two concepts (the portable query and the 20-account cap). Filters like to/from/read/starred/folder and the per-account pageToken structure get no explanation anywhere, so the description fails to compensate for the coverage gap.

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 (search) and resource (emails) with a clear scope: batching up to 20 accounts in one portable query and returning grouped results. This implicitly distinguishes it from the single-account search_emails sibling, though it never names the alternative.

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

Usage Guidelines3/5

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

The 20-account cap and 'one portable query' framing imply this is the multi-account tool, but there is no explicit when-to-use vs search_emails guidance or any stated prerequisites. Usage must be inferred from the batch scope.

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