Inbox Triage

Load a page of the inbox view

inbox_view_page

Read-onlyIdempotent

Used by the interactive inbox view to switch inbox tabs, filters, and pages. Agents should call show_inbox.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inbox_view_page"
  }
}

Input Schema

Name	Required	Description
`inbox`	No	Inbox name (like "Work Gmail"), inbox id, or leave empty for all inboxes combined
`limit`	No	Rows per page, 1 to 50. Default 25.
`since`	No	ISO time. Applies to whichever filter is set, not only "since": combine it with any filter for a single call ("newsletters from this week" is filter: newsletters, since: <start of this week>). For filter "since" alone, defaults to when the person last finished triage.
`filter`	No	needs (default: unread or VIP mail in the inbox, newsletters left out, unread automated mail older than attentionDays left out), vip, newsletters, today, since (since the last triage), all, reply: mail from a person addressed to you that you have not answered
`offset`	No
`inboxId`	No
`timeZone`	No	The person's IANA time zone, like America/Chicago, so "today" means their calendar day. Without it, "today" is the last 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful context that it belongs to the interactive inbox view and should not be used by agents, but it does not add much beyond that about behavior such as pagination or return semantics.

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 short sentences with no filler. The intended context and the agent redirection are both front-loaded and easy to act on.

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 UI-internal page loader, the definition is complete enough to prevent agent misuse by naming show_inbox as the correct alternative. It does not explain return values or pagination details, but there is no output schema and the schema covers most parameters.

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 71%, so most parameters are documented in the schema, including inbox, limit, since, filter, and timeZone. The description only broadly alludes to tabs, filters, and pages, adding little parameter-specific meaning beyond the schema.

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?

The description states that the tool is used by the interactive inbox view to switch inbox tabs, filters, and pages, which gives a clear verb-and-resource purpose. It also distinguishes itself from the agent-facing alternative by directing agents to show_inbox, though the wording is somewhat meta rather than fully specifying what the tool returns.

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

Usage Guidelines5/5

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

It explicitly tells agents not to use this tool for agent workflows and to call show_inbox instead, which is a clear when-not-to-use statement with a named alternative. The intended interactive-UI context further clarifies the usage boundary.

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?