Skip to main content
Glama
HuntsDesk

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

get_events

Retrieve calendar events by ID or list events within a time range with optional keyword filter.

Instructions

Fetch events from a calendar — one by ID, or a filtered range.

Two modes: (1) pass event_id to retrieve a single event (range/query params ignored); (2) omit event_id to list events in a time window, optionally filtered by keyword. For free/busy scanning across many calendars use query_freebusy instead. For creating/updating events use manage_event. Requires the calendar.readonly OAuth scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
calendar_idNoCalendar ID from list_calendars, or "primary" for the user's main calendar. Default "primary".primary
event_idNoSpecific event ID to fetch. From a prior get_events call or a calendar URL like calendar.google.com/calendar/u/0/r/eventedit/<id>. When set, all range/query filters are ignored.
time_minNoRange start, RFC3339 (e.g. "2026-05-01T00:00:00Z" or "2026-05-01"). Defaults to now when omitted.
time_maxNoRange end, RFC3339 exclusive. Omit for open-ended range (capped by max_results).
max_resultsNoCap on events returned, 1-2500. Default 25.
queryNoFree-text filter matched against summary, description, and location.
detailedNoFalse returns just summary + times + link; True adds description, location, attendees with response status, and organizer.
include_attachmentsNoWhen detailed=True, also include attachment fileId/fileUrl/mimeType/title for events with attached Drive files. Ignored when detailed=False.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv1.0.0
    • changedInput schema / properties / calendar_id / description
      Previous value: -"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`."New value: +"Calendar ID from list_calendars, or \"primary\" for the\nuser's main calendar. Default \"primary\"."
    • changedInput schema / properties / detailed / description
      Previous value: -"Whether to return detailed event information including description, location, attendees, and attendee details (response status, organizer, optional flags). Defaults to False."New value: +"False returns just summary + times + link; True adds\ndescription, location, attendees with response status, and\norganizer."
    • changedInput schema / properties / event_id / description
      Previous value: -"The ID of a specific event to retrieve. If provided, retrieves only this event and ignores time filtering parameters."New value: +"Specific event ID to fetch. From a prior get_events call\nor a calendar URL like calendar.google.com/calendar/u/0/r/eventedit/<id>.\nWhen set, all range/query filters are ignored."
    • changedInput schema / properties / include_attachments / description
      Previous value: -"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."New value: +"When detailed=True, also include attachment\nfileId/fileUrl/mimeType/title for events with attached Drive\nfiles. Ignored when detailed=False."
    • changedInput schema / properties / max_results / description
      Previous value: -"The maximum number of events to return. Defaults to 25. Ignored if event_id is provided."New value: +"Cap on events returned, 1-2500. Default 25."
    • changedInput schema / properties / query / description
      Previous value: -"A keyword to search for within event fields (summary, description, location). Ignored if event_id is provided."New value: +"Free-text filter matched against summary, description, and\nlocation."
    • changedInput schema / properties / time_max / description
      Previous value: -"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."New value: +"Range end, RFC3339 exclusive. Omit for open-ended range\n(capped by max_results)."
    • changedInput schema / properties / time_min / description
      Previous value: -"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."New value: +"Range start, RFC3339 (e.g. \"2026-05-01T00:00:00Z\" or\n\"2026-05-01\"). Defaults to now when omitted."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"The user's Google email address. Required."New value: +"The user's Google email address (authenticated\naccount)."
  2. First observedv1.19.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It explains mode behavior, parameter interactions (event_id overrides range), defaults, and filtering. Slightly missing details on pagination or error handling, but largely transparent.

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 concise (3 sentences) with clear structure: mode breakdown, sibling tool references, and auth note. No filler words; every sentence adds value.

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?

Given the presence of output schema, return values need not be detailed. The description covers modes, parameters, filtering, and auth. Minor omission: no mention of pagination or error states, but it's sufficient for a read tool with good schema coverage.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the two modes and how event_id overrides range/query params, and clarifies time_min default and max_results cap. This goes beyond schema descriptions.

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 clearly states the tool fetches calendar events by ID or filtered range, specifying two modes. It distinguishes itself from siblings like query_freebusy and manage_event, providing a precise verb+resource+scope definition.

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?

Explicitly details when to use each mode (event_id vs. time window), mentions alternatives (query_freebusy for free/busy, manage_event for create/update), and lists required OAuth scope. Clear guidance for agent selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HuntsDesk/ve-gws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server