Google Workspace MCP Server

Overview Schema Source Related Servers Discussions Admin

get_events

Fetch Google Calendar events by ID, time range, or keyword to access meeting details, attendee info, and attachments.

Instructions

Retrieves events from a specified Google Calendar. Can retrieve a single event by ID or multiple events within a time range. You can also search for events by keyword by supplying the optional "query" param.

Args: user_google_email (str): The user's Google email address. Required. calendar_id (str): The ID of the calendar to query. Use 'primary' for the user's primary calendar. Defaults to 'primary'. Calendar IDs can be obtained using list_calendars. event_id (Optional[str]): The ID of a specific event to retrieve. If provided, retrieves only this event and ignores time filtering parameters. time_min (Optional[str]): The start of the time range (inclusive) in RFC3339 format (e.g., '2024-05-12T10:00:00Z' or '2024-05-12'). If omitted, defaults to the current time. Ignored if event_id is provided. time_max (Optional[str]): The end of the time range (exclusive) in RFC3339 format. If omitted, events starting from time_min onwards are considered (up to max_results). Ignored if event_id is provided. max_results (int): The maximum number of events to return. Defaults to 25. Ignored if event_id is provided. query (Optional[str]): A keyword to search for within event fields (summary, description, location). Ignored if event_id is provided. detailed (bool): Whether to return detailed event information including description, location, attendees, and attendee details (response status, organizer, optional flags). Defaults to False. include_attachments (bool): Whether to include attachment information in detailed event output. When True, shows attachment details (fileId, fileUrl, mimeType, title) for events that have attachments. Only applies when detailed=True. Set this to True when you need to view or access files that have been attached to calendar events, such as meeting documents, presentations, or other shared files. Defaults to False.

Returns: str: A formatted list of events (summary, start and end times, link) within the specified range, or detailed information for a single event if event_id is provided.

Input Schema

TableJSON Schema

Name	Required	Default
`query`	No
`detailed`	No
`event_id`	No
`time_max`	No
`time_min`	No
`calendar_id`	No	primary
`max_results`	No
`user_google_email`	Yes
`include_attachments`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.14.3Sep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys that this is a read/retrieve operation, explains default behaviors (time_min current time, max_results 25, detailed False), and clarifies edge behavior such as ignored parameters when event_id is present. It stops short of mentioning auth requirements or error conditions, but otherwise is quite transparent.

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?

The description is longer than average, but it needs to be: 9 parameters, multiple retrieval modes, and conditional behaviors require explanation. The opening sentence front-loads the core purpose, and the Args section is organized consistently. Some values repeat the schema defaults, but the extra explanatory context justifies the length.

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 9-parameter tool with no annotations, the description covers all invocation-relevant details: required email, calendar selection, retrieval modes, filtering, detailed output, attachments, and return format. It does not mention prerequisites like authentication or behavior when no events are found, but the provided information is sufficient for correct use in most cases.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description documents all 9 parameters in detail, including defaults, formats (RFC3339), conditions (ignored if event_id is provided), and usage notes (include_attachments only with detailed=True). This fully compensates for the schema's lack of parameter descriptions and adds practical guidance beyond JSON structure.

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 opens with a clear verb and resource: 'Retrieves events from a specified Google Calendar.' It then specifies the two main retrieval modes (single event by ID, multiple events by time range) plus keyword search, making the tool's purpose immediately distinguishable from related calendar tools like manage_event or query_freebusy.

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 operational context: when event_id is provided, time filtering params are ignored; time_min defaults to current time; include_attachments is recommended when attachment access is needed; and calendar IDs can be obtained via list_calendars. It does not explicitly contrast with query_freebusy or other calendar alternatives, but the usage conditions for each mode are well explained.

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

Deploy Server