Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

calendar_events_list

Read-only

Retrieve and filter calendar events by calendar ID, time range, search query, and sort order to view schedules or expand recurring events.

Instructions

List events from a calendar.

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": {
      "calendarId": "<calendarId>"
    },
    "name": "calendar_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search
orderByNoSort order: startTime or updated
timeMaxNoUpper bound (RFC3339)
timeMinNoLower bound (RFC3339, e.g. "2026-03-07T00:00:00Z")
calendarIdYesCalendar ID (use 'primary' for main calendar)
maxResultsNoMax events to return
singleEventsNoExpand recurring events (usually true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that – no mention of pagination, recurrence expansion behavior, default result limits, or auth scoping.

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

Conciseness3/5

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

It is a single short sentence with no wasted words, but its brevity reflects under-specification rather than disciplined conciseness; there is no structure to speak of.

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?

For a 7-parameter listing tool with no output schema, the description should at minimum signal that time bounds are commonly supplied and that results may be paginated. It leaves an agent to infer everything from the schema.

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%, and each parameter already carries a clear description including RFC3339 format and the 'primary' calendar convention. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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 and resource ('List events from a calendar'), which is enough to tell it apart from calendar_events_get in practice. It does not explicitly name or differentiate itself from siblings, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no mention of when to use this versus calendar_events_get or calendar_freebusy_query, no prerequisites, and no note about required time bounds.

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