Inbox Triage

Sync one inbox now

sync_inbox

DestructiveIdempotent

Fetches the newest ~300 messages per selected folder for iCloud/IMAP/Microsoft (Gmail's stored window grows to 300 over its first syncs, 40 newest per sync; default: INBOX + Sent + Drafts) and replaces the local window for each. Pass folders to override (and persist) the inbox's selected folder scope for this and future syncs. Use list_folders first to get the canonical folder ids/names for this account. The spam check runs during the sync: obvious spam and scams go straight to the mailbox's Spam folder, and mail that only looks like junk or a scam gets a junkHint on its row (nothing is moved). Returns demo data marked isDemo:true if no credential is stored yet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inboxId": "<inboxId>"
    },
    "name": "sync_inbox"
  }
}

Input Schema

Name	Required	Description	Default
`folders`	No	Overrides (and persists) the inbox's selected folders for this sync, e.g. from list_folders output. At most 25 folders.
`inboxId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that the local window is replaced per folder, per-provider fetch windows (Gmail 40/sync growing to 300), and a significant side effect — spam/scam mail is moved to the Spam folder during sync while borderline mail only gets a junkHint. Also discloses the demo-data fallback when no credential exists, which the destructive/openWorld annotations cannot convey.

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?

Front-loaded with the core fetch behavior and sized roughly to the tool's complexity; each clause (provider windows, defaults, persistence, spam routing, demo fallback) carries distinct information. A single dense paragraph makes the spam-routing side effect and demo fallback slightly hard to scan.

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?

For a destructive, open-world mutation with no output schema, the description covers the important behavioral surface (what is replaced, what gets moved, junkHint, isDemo). It omits the actual return shape (counts, per-folder results) and where to obtain `inboxId`, which an agent needs for correct invocation.

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

Parameters4/5

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

With 50% schema coverage, the description meaningfully compensates for `folders` — default scope (INBOX + Sent + Drafts), persistence across future syncs, per-folder cap context, and the list_folders source for canonical ids. `inboxId` remains undocumented in both schema and description (no hint that list_inboxes supplies it), which is the remaining gap.

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?

States a specific verb and resource ('Fetches the newest ~300 messages per selected folder ... replaces the local window'), plus the exact providers (iCloud/IMAP/Microsoft) and default folder scope. This clearly distinguishes it from siblings like list_folders (enumeration) and load_older_messages (backfill).

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?

Gives an explicit prerequisite ('Use list_folders first to get the canonical folder ids/names') and explains how passing `folders` changes behavior and persists. It does not state when NOT to sync or contrast with load_older_messages / search_mailbox alternatives, so it stops short of full routing guidance.

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

All Inbox Triage 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?