mailbox

list_inbound_mail

Read-onlyIdempotent

List forwarded inbound mail items captured from private forwarding aliases. Default output includes compact draft_context so an LLM or external agent can reason about OCR context, reply contact candidates, deadlines, and thread linkage before generating outbound mail.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of inbound items to return (1-100).
`offset`	No	Number of inbound items to skip for pagination.
`status`	No	Optional inbound status filter.
`include`	No	Optional expansions. Defaults to ["drafting"]. Add ocr/lineage only when deeper provenance is needed.
`category`	No	Optional category filter such as "Needs review" or "Loan / Mortgage".
`thread_id`	No	Only return inbound items linked to this postal mail thread.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Forwarded inbound mail items plus pagination.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": true,
+      "description": "Forwarded inbound mail items plus pagination.",
+      "properties": {
+        "inbound_mail": {
+          "description": "Forwarded inbound mail items with optional draft context.",
+          "items": {
+            "additionalProperties": true,
+            "description": "One returned record.",
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "pagination": {
+          "additionalProperties": false,
+          "description": "Pagination metadata for the current result set.",
+          "properties": {
+            "has_more": {
+              "description": "Whether another page is available.",
+              "type": "boolean"
+            },
+            "limit": {
+              "description": "Maximum records requested.",
+              "type": "integer"
+            },
+            "offset": {
+              "description": "Records skipped before this page.",
+              "type": "integer"
+            },
+            "total": {
+              "description": "Total matching records when available.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "inbound_mail",
+        "pagination"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

AddedMay 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds non-redundant behavioral context by revealing that the default output includes a compact draft_context with specific elements (OCR context, reply contact candidates, deadlines, thread linkage), which helps an agent understand what the tool returns beyond the schema.

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?

Two concise sentences: the first states the core function, the second explains the default output's purpose. Every word earns its place with no fluff or repetition.

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

Completeness4/5

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

Given the tool has a rich output schema and comprehensive annotations, the description is complete enough for an agent to know what the tool does, when to use it, and what to expect in the default output. It doesn't need to explain return values or pagination, as those are covered by the output schema and input schema. A minor gap is not explicitly contrasting with related list tools.

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 baseline is 3. The description mentions 'Default output includes compact draft_context,' which aligns with the include parameter's default, but it does not add substantial meaning to any individual parameter beyond what the schema already documents.

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

Purpose5/5

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

The description uses a specific verb ('List') and identifies the resource ('inbound mail items') with a precise qualifier ('forwarded ... captured from private forwarding aliases'), clearly differentiating it from sibling tools like list_outbound_mail and get_inbound_mail.

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 description explicitly states a use case: 'so an LLM or external agent can reason about OCR context, reply contact candidates, deadlines, and thread linkage before generating outbound mail.' This gives clear context for when to use the tool, though it doesn't explicitly name alternatives or exclusion criteria.

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

All mailbox 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?