Skip to main content
Glama
Sign In
Gmail Multi-Inbox MCP Server

Gmail Multi-Inbox MCP Server

by tszaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_events

Lists calendar events across Gmail accounts. Filter by time range, text query, or specific account to locate events quickly.

Instructions

List calendar events. Omitting account aggregates across all enabled accounts. Supports time range and text search.

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": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFree text search query.
accountNoOptional account id.
time_maxNoUpper bound for event end time (RFC3339).
time_minNoLower bound for event start time (RFC3339, e.g. "2025-01-01T00:00:00Z").
calendar_idNoCalendar ID (default "primary").
max_resultsNoMaximum events to return (1-250, default 25).
single_eventsNoExpand recurring events into single instances (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.2

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are present, so the description carries the burden. It discloses the key aggregation behavior and filter capabilities, but omits details like default time boundaries, output format, or permissions. For a list operation, safety is implied, but transparency is only partial.

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?

The description is three short sentences, each earning its place: the purpose, the aggregation behavior, and the filter capabilities. It is front-loaded and contains no filler.

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

Completeness3/5

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

The tool has 7 optional parameters, no annotations, and no output schema. The description covers the main filtering behavior but leaves ambiguity about what the list returns and default time-range behavior when time_min/time_max are omitted. This makes it adequate but not fully complete.

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?

Schema descriptions already cover all 7 parameters, earning a baseline of 3. The description adds value beyond the schema by explaining that omitting account aggregates across all enabled accounts, and explicitly confirms query as text search.

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 is explicit: "List calendar events" is a clear verb+resource pair. It distinguishes from sibling tools like get_event (single event) and list_calendars (calendar metadata), and adds the scoping nuance of account aggregation.

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 provides clear context on when to use the tool: supports time range and text search, and explains the account-omission aggregation behavior. It does not explicitly name alternatives, but the context is sufficient given siblings like get_event.

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

Deploy Server

Other Tools